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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context beyond these: payment via prepaid credit, interaction with official Brazilian sources, non-confidential data, and LGPD data controller responsibilities. No contradictions 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 description is a single block of text containing multiple clauses. It includes essential purpose at the start but then mixes in legal and payment details. It is not overly long, but it could be better structured with the purpose first and operational details separated. Some content, like LGPD specifics, may be tangential for tool invocation.

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?

With no output schema and two undocumented parameters, the description is incomplete. It does not explain what the response contains, how the parameters relate to the query, or any prerequisites (e.g., needing a CPF or CNPJ). For a data query tool, this is insufficient for an agent to understand expected inputs and outputs.

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%, so the description must explain the parameters (cpf and cnpj). It does not. There is no mention of what these fields are, that at least one is typically required, or any formatting instructions. This is a critical gap for an agent to invoke the tool correctly.

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 what the tool does: it consults a Certidão Negativa de Débitos (negative debt certificate) from the official source of Prefeitura GO Itumbiara. The verb 'consultar' and the resource are explicit, and it is easily distinguished from the generic sibling tools like authenticate or marketplace.

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 about usage conditions (hosted by platform, prepaid credit, no credentials, LGPD compliance) but does not explicitly state when to use this tool versus alternatives. Since the siblings are unrelated system tools, the intended use case is implied by the specific municipality and certificate type, but no explicit exclusions are given.

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