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

The annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds useful behavioral context: there is a cost per consultation, no platform credentials are required, the data comes from official public sources, and the client is responsible for LGPD compliance and legitimate purpose.

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 compact and front-loaded: the first sentence states the tool's purpose, and the remaining sentences add essential operational and legal details. Every sentence contributes useful context without repetition or padding.

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 description provides strong context for choosing the tool and understanding the legal/financial implications. However, with four undocumented parameters and no output schema, there are clear gaps around correct invocation and expected return behavior.

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 explain cpf, cnpj, outra, or finalidade. It leaves the agent unsure which identifier should be provided, whether one or multiple allowed, what 'outra' means, and how 'finalidade' should be used.

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 a specific action and resource: consulting the Certidão Negativa de Débitos from Prefeitura de Palmas via an official source. It is specific enough to distinguish itself from the unrelated sibling tools 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?

It provides clear operational context: the tool is a paid, prepaid-credit consultation of official Brazilian public sources, requires no platform credentials, and is not secret data. It does not explicitly mention when not to use it, but the intended use case is clearly stated and the siblings are unrelated.

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