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

Annotations already indicate read-only and idempotent behavior, and the description confirms these by describing a consultation of public (non-sensitive) data. It adds context about hosting and no credentials, but lacks detail on data return format or potential limitations. No contradiction.

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 one long sentence that covers multiple points (purpose, hosting, payment, data ownership) but lacks clear structure. It is somewhat verbose but not excessively long; however, breaking into sentences would improve readability.

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 read-only consult tool with no output schema, it explains the general behavior well. It covers the fact that it uses pre-paid credit and that the client is data controller. However, it omits the return format, any error handling, and details on how the four parameters are used, making it incomplete for an agent expecting clear selection.

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 all four parameters are plain strings with no descriptions. The tool description mentions parameters implicitly (cpf, cnpj, im, inscricao_imovel) but does not explain their formats or business meaning. It fails to compensate for the lack of schema information.

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 it consults a Certidão Negativa de Débitos from an official source, which is specific and useful. It does not explicitly differentiate from sibling tools, but the operation and target are clear.

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 does not state when to use this tool versus alternatives. The description mentions it covers official Brazilian sources, but no explicit exclusion or alternative guidance is provided. Use-case inference only.

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