CNAE Economic Activity Classes

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds useful context: it indicates the data source (IBGE), usage (CNPJ/tax filings), and licensing (CC BY 4.0), going beyond what annotations provide.

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 just two sentences, front-loads the purpose, and includes essential context without waste. Every sentence is informative.

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 the tool's simplicity (one optional parameter, output schema present), the description sufficiently explains what the tool returns and its context. It could be slightly more explicit about retrieving the full list, but it is adequate.

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 of the single parameter 'limit' is 100% with a clear description. The tool description does not add any additional meaning for parameters, so it meets the baseline.

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?

Description clearly states the tool provides Brazilian CNAE economic activity classification codes, a specific verb and resource. It distinguishes from siblings like gov.ibge.municipalities by focusing on economic activity codes used in CNPJ and tax filings.

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 implies the tool is for retrieving CNAE codes for economic activity classification, which is clear given the name. It does not explicitly state when to use alternatives, but the purpose is distinct from other gov.ibge tools.

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