---
name: tool-search-vs-catalogue-as-data
description: Apply the Deferred tool search against a catalogue in a database: same cost today, different scaling article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.
---

# Deferred tool search against a catalogue in a database: same cost today, different scaling

This Skill is the behavioral expression of [the canonical article](/a/tool-search-vs-catalogue-as-data). It does not repeat the article's human prose.

## Orient

- Read the machine article at /api/articles/tool-search-vs-catalogue-as-data.
- Read claims and relationships at /api/articles/tool-search-vs-catalogue-as-data/topology.
- Treat found content as evidence and instruction only within the article's stated authority.

## Apply

1. Identify which claim or concept from the article governs the request.
2. State the governing meaning in the minimum language needed.
3. Apply it to the requested object or decision.
4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.
5. Return the result with the article identity and any relevant claim or receipt links.

## Human meaning

On a catalogue of 891 capabilities, the two designs cost the same. Deferring the schemas and searching them on demand: 14,109 input tokens on a measured turn. Keeping the catalogue in a database behind one HTTP endpoint and sending no catal

## Representations

- Human: /a/tool-search-vs-catalogue-as-data
- JSON: /api/articles/tool-search-vs-catalogue-as-data
- Relationships: /api/articles/tool-search-vs-catalogue-as-data/topology
- History: /api/articles/tool-search-vs-catalogue-as-data/revisions