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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint=false. The description adds that it is a paid query, hosted by the platform without credentials, and clarifies LGPD compliance. It also states the data is not confidential, which is useful. No contradictions with annotations; description adds behavioral context beyond 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 a single block of text with three sentences. It is relatively concise but includes some redundancy (e.g., 'consulta em fonte oficial' and later 'fontes e órgãos oficiais brasileiros'). It is front-loaded with the main purpose, but the sentence about LGPD could be seen as extraneous for tool description.

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 is a read-only query with some legal and payment context, the description covers essential information such as payment, data source, and LGPD compliance. However, with no output schema and zero parameter descriptions, it lacks completeness regarding input expectations and return format. The absence of any output schema makes it harder to know what the result contains.

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 0% and there are 6 parameters with no descriptions in the schema. The description does not explain any parameter semantics; it only hints at CPF/CNPJ usage by mentioning taxpayer. It does not clarify parameters like finalidade, nome_requerente, or the requester fields. This is a significant gap.

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?

Description clearly states the tool performs a CND consultation (Certidão Negativa de Débitos) for taxpayers in Maringá-PR, with a clear verb ('consultar') and resource (debt clearance certificate). It also clarifies the data source (official Brazilian sources) and type of data (non-confidential). However, it does not explicitly differentiate from sibling tools, but siblings are generic system tools, so no real overlap.

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 mentions that payment is required via prepaid credits and that the client is the data controller under LGPD, implying use cases. However, it does not state when to use this tool versus alternatives, nor provide explicit conditions or exclusions. The context is somewhat clear but lacks alternative guidance.

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