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 those: payment with prepaid credit, no platform credentials needed, data is public/non-confidential, and LGPD responsibility lies with the client. This meaningfully supplements the annotation-level safety profile.

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 three sentences with front-loaded purpose, then payment/hosting context, then data and legal notes. It is efficient and well-structured, though the LGPD detail could be more concise. Every sentence adds some value, but the legal sentence is secondary.

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, so the description should at least hint at the result format; it does not. It does cover the data source, payment model, and legal accountability. However, the lack of parameter guidance and return-value description leaves gaps for a paid consultation tool.

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 the description does not mention the cpf or cnpj parameters at all. While the parameter names are self-explanatory Brazilian identifiers, the description fails to clarify whether either is required, if they are alternatives, or how the query uses them. The description carries no burden for parameters, creating a 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?

The description clearly states the tool performs a 'consulta' (query) of 'Certidão Negativa de Débitos' from a specific official source (Prefeitura SC Balneário Camboriú), using a specific verb and resource. It is clearly distinct from the generic sibling tools like 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: this is a paid per-query service using prepaid credits, hosted on the platform without requiring platform credentials. It does not explicitly state when-not-to-use or name alternatives, so it stops short of a 5, but the usage context is unambiguous.

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