consultar_empresa_completa

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

No annotations are provided, so the description must fully convey behavioral traits. It indicates a read operation but does not disclose potential side effects, rate limits, error handling for invalid CNPJs, or prerequisites. This gap leaves the agent underinformed.

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 two sentences long, stating the purpose and listing outputs. No redundant information, front-loaded, and appropriate for a simple query tool.

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 simple parameter and presence of an output schema, the description covers the core functionality well. It lacks guidance on usage scenarios and error conditions, but overall it is sufficiently complete for a quick query tool.

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?

With 100% schema coverage for the single parameter 'cnpj', the description adds marginal value beyond the schema. It contextualizes that the CNPJ is from two sources but does not enhance parameter understanding significantly.

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 it 'consulta dados enriquecidos' (queries enriched data) combining Receita Federal and Simples Nacional, listing specific return fields. It distinguishes from siblings like 'consultar_simples_nacional' and 'analyze_cnpj_compliance' by its comprehensive scope.

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 use for comprehensive company data queries, but lacks explicit guidance on when to prefer this tool over siblings or when not to use it, such as for simple compliance checks or authority-specific lookups.

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