ibge_cnae

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

The description explicitly states the behavior: 'read-only and idempotent — a live GET against the public IBGE CNAE API. Returns Markdown.' This aligns with and adds detail beyond annotations (readOnlyHint, idempotentHint), providing full transparency.

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 well-structured with bullet points and examples, though slightly long. It is front-loaded with purpose and hierarchy, but every sentence adds value. No unnecessary repetition.

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?

Given annotations, input schema, and output schema presence, the description covers all necessary context: behavior, return format, hierarchical levels, and usage examples. It is fully sufficient for an agent to invoke the tool correctly.

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% with detailed descriptions for each parameter. The description adds value by providing concrete examples of parameter usage (e.g., 'busca="software"', 'codigo="6201-5/01"'), which helps the agent understand how to invoke the tool correctly.

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 tool queries CNAE classifications from IBGE, with specific verb 'Queries' and resource 'CNAE'. It provides hierarchical structure and examples, distinguishing it from sibling tools that handle other IBGE data.

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 lists features and examples that clarify when to use the tool (e.g., search by code, description). It does not explicitly state when not to use it or compare with alternatives, but the context of sibling tools makes the purpose clear.

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