buscar_cnae

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

With no annotations, the description carries the transparency burden. It explains the search behavior and the output (list of subclasses). It does not mention error handling or edge cases, but for a simple search tool, this is adequate.

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?

The description is concise and well-structured, with no unnecessary words. It conveys the purpose, method, and value in three short sentences.

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?

The description fully covers the tool's function and expected output for its simple scope. It does not require additional context about return format or limitations, as it is a straightforward search operation.

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?

The schema description for the 'texto' parameter is explicit and helpful, including examples ('software', 'restaurante'). No additional explanation is needed beyond what the schema provides.

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 action ('Busca' - searches), the resource ('atividades econômicas CNAE'), and the result (returns a list of subclasses). It distinguishes itself from sibling tools like 'consultar_cnae' which likely fetches details by 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 provides a clear use case ('Útil para encontrar o código CNAE a partir do ramo de atividade desejado'). It does not explicitly mention when not to use it or contrast with 'consultar_cnae', but the guidance is sufficient for typical usage.

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