buscar_cnae

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It states it returns a list of subclasses but does not mention side effects, auth requirements, rate limits, or pagination. For a read-only search tool, this is adequate but could be more explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, front-loaded with the core action and return type. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple text search tool with an output schema (not shown), the description covers input and output adequately. It could mention result limits or error handling, but the tool's simplicity makes this a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% as the required parameter 'texto' has a description with examples. The description only rephrases 'por texto na descrição', adding little beyond the schema. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Busca' (search) and the resource 'atividades econômicas CNAE por texto na descrição'. It distinguishes from sibling consultar_cnae by specifying it returns a list of subclasses matching a textual query, rather than querying by a specific code.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description says 'Útil para encontrar o código CNAE a partir do ramo de atividade desejado', which gives clear context for when to use. However, it does not explicitly mention when not to use it or suggest sibling alternatives like consultar_cnae for code lookups.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.