consultar_empresa

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

No annotations are provided, so the description carries the full burden. 'Consulta' implies a read operation, but the description does not disclose return data format, behavior when the company is not found, data freshness, or any side effects. It adds minimal behavioral context beyond the verb.

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 a single, concise sentence that immediately states the tool's action and scope. No filler or redundant information is present.

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?

This is a simple one-parameter lookup, but with no output schema or annotations, the vague term 'dados' leaves out what data is returned and how errors are handled. It is adequate for a minimal lookup but lacks useful operational context.

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 input schema already has 100% description coverage for the single parameter ('CPF ou CNPJ da empresa'). The tool description adds no additional format, validation, or usage detail, so the baseline score of 3 is appropriate.

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 uses a specific verb ('Consulta') and identifies the resource ('dados de uma empresa cadastrada na Nuvem Fiscal'), clearly distinguishing this internal company lookup from the sibling tool 'consultar_cnpj' which likely queries external CNPJ 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?

No guidance is provided about when to use this tool versus alternatives like 'consultar_cnpj' or 'cadastrar_empresa'. There are no explicit exclusions, prerequisites, or contextual instructions.

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