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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds meaningful context beyond this: prepaid per-query cost, no platform credentials needed, public non-confidential data, and LGPD responsibilities. No contradictions with annotations. It could mention rate limits or response details, but the added context is strong.

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 purpose is front-loaded in the first sentence, and the remaining sentences are short and relevant. The LGPD clause is somewhat secondary but still contextually useful. No wasted filler.

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?

The tool has no output schema and only 2 params with zero description coverage. The description fails to explain how to provide CPF/CNPJ or what the response contains. While annotations cover safety traits, the agent still lacks critical invocation information.

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 coverage is 0% and the description provides no explanation of the cpf/cnpj parameters. It does not state formats, requiredness, mutual exclusivity, or which identifier applies to which scenario. The description adds zero value beyond the raw schema property names.

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 identifies the resource: SEFAZ MT Certidão Negativa de Débitos reprint/consultation. The verb 'consultar' appears in the name and 'consulta em fonte oficial' reinforces the action. It is clearly distinct from the sibling tools, which are generic platform utilities.

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 intended use is implied: query an official Brazilian tax debt certificate. It adds useful context about being hosted, prepaid, and credential-free, but it does not explicitly state when to use this tool versus alternatives or when not to use it.

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