consultar_cnpj

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

There are no annotations, and the description does not disclose behavioral details such as read-only nature, required authorization, failure modes, or rate limits. It states outputs but omits important operational context.

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, well-structured, and free of unnecessary detail. It clearly communicates the tool's purpose and expected outputs 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 lists the main returned fields, which is helpful since there is no output schema. However, it does not mention error scenarios, invalid CNPJ handling, or whether partial data is possible, leaving some contextual gaps.

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 already fully describes the single parameter, including format and examples. The description adds no additional semantic information beyond what is already in the schema, so the baseline score applies.

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 (consultar) and resource (CNPJ) and lists the main returned fields. However, it does not differentiate this tool from the sibling consultar_empresa_completa, which may overlap significantly.

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 gives no guidance on when to use this tool instead of related alternatives such as consultar_empresa_completa or analyze_cnpj_compliance. It only mentions input formatting, which is more parameter-level guidance.

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