consultar_empresas_lote

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

The description mentions error handling per CNPJ, but lacks details on read-only nature, rate limits, or authentication requirements. With no annotations, full burden is on description which gives only partial 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?

Two concise, front-loaded sentences conveying essential information without fluff.

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 has an output schema and two parameters, the description provides adequate context for the main purpose and error behavior, but the missing parameter documentation and lack of prerequisites reduce completeness.

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 description explains the 'cnpjs' parameter (multiple CNPJs) but completely omits the 'criterios_estritos' boolean parameter. With 0% schema coverage, the description should compensate but does not fully.

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 performs batch queries on multiple CNPJs and returns compliance summaries and supplier risk scores. It distinguishes from siblings like 'consultar_cnpj' (single query) and other specific tools.

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 provides a clear use case ('quick screening of supplier portfolio'), but does not explicitly exclude alternatives or give conditions when not to use.

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