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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context beyond annotations: the query is official and citizen-accessible, paid per consultation via prepaid credit, does not use platform credentials, and involves LGPD data-control responsibilities. No contradiction with 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 main purpose is front-loaded in the first sentence, and subsequent sentences add useful context about cost, credentials, data sensitivity, and LGPD. Slight redundancy exists between 'fonte oficial' and 'fontes e órgãos oficiais brasileiros', but overall the description is compact and readable.

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 tool with 7 parameters and no output schema, the description is incomplete. It does not explain what the consulted certificate looks like, what return format the agent can expect, nor how the various login and PKCS#12 parameters should be supplied or chosen. Annotations cover safety traits, but operational completeness is lacking.

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 schema has 7 parameters with 0% description coverage, and the description provides no per-parameter guidance. Parameter names like cpf, cnpj, ie, login_cpf, login_senha, pkcs12_cert, and pkcs12_pass are somewhat self-explanatory, but the description does not clarify which identifiers are required, whether credential parameters are alternatives or complements, or expected formats.

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 opens with the specific resource ('Certidão Negativa de Débitos' from SEFAZ MG) and the operation ('consulta em fonte oficial'). This clearly distinguishes the tool from unrelated siblings such as authenticate, marketplace, and report_bug.

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 clear context for use: it queries official Brazilian sources, requires prepaid credit rather than platform credentials, and concerns non-confidential data. It does not explicitly list exclusions or alternatives, but the use case is made apparent and context-rich.

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