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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds valuable context: payment per query with prepaid credit, non-confidential data (same as available to citizens), and LGPD controller responsibility. This goes beyond the structured annotations without contradicting them.

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 only a few sentences, front-loaded with the core purpose, and each sentence adds relevant context (payment model, data nature, legal responsibility). There is no redundancy or fluff.

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?

While the tool's function is clear, the description lacks essential parameter guidance and does not describe the output or return format. Given that there is no output schema and four parameters (two required), the description is incomplete for safe and correct invocation.

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 does not mention any of the four parameters (cpf, cnpj, tipo_certidao, finalidade_certidao). With zero coverage in both schema descriptions and the text, the agent has no guidance on how to fill required fields or what values are expected.

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 queries a Negative Debt Certificate (Certidão Negativa de Débitos) from Balsas city hall, using the specific verb 'consulta' and a defined resource. This differentiates it from the sibling tools like authenticate, connect, and marketplace, which have unrelated purposes.

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 context that this is a paid query tool for official Brazilian sources and that it does not require platform credentials. However, it does not explicitly mention alternatives or when-not-to-use, but since sibling tools are not similar query tools, the usage context is sufficiently clear.

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