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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior; the description adds practical context with 'Cache 1h' and the endpoint path '/api-de-dados/cnep'. This gives the agent useful information about possible data staleness and the technical route, with no contradiction against the annotations.

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 compact and front-loaded with the core purpose. However, 'Lei Anticorrupção' and 'Empresas punidas' are mentioned twice in consecutive lines, creating minor redundancy.

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?

For a low-complexity query tool with a fully documented input schema, rich annotations, and an existing output schema, the description covers semantics, endpoint, and cache behavior adequately. The main missing piece is sibling differentiation, which is already penalized under usage guidelines.

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 description coverage is 100%, and all three parameters (cnpj, nome, pagina) already have meaningful descriptions. The tool description adds no parameter-specific 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?

States a specific verb ('Consulta') and resource ('CNEP — Cadastro Nacional de Empresas Punidas'), and clarifies the legal basis (Lei 12.846/2013) and integrity-risk semantics. Though it does not explicitly compare with sibling sanction tools such as CEIS or CEAF, naming the exact registry makes the purpose distinct and clear.

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 explicit when-to-use or alternative routing is provided. The description gives background context (punished companies, integrity risk) but never states when to prefer CNEP over compras_checar_sancoes_fornecedor or the other compras_sancao_* registries. This is effectively no usage guidance.

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