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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds non-obvious behavioral details: it is pay-per-query, requires no platform credentials, and involves LGPD data-controller responsibilities. This goes beyond the annotation metadata and enhances understanding of side effects and compliance needs.

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, dense paragraph covering key points: functionality, hosting, payment, data source, and legal compliance. While a bit long, each clause provides relevant context and it is front-loaded with the core purpose. It could be split for readability, but it remains efficient.

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 only 0% parameter descriptions, the description should at least hint at return types or parameter semantics; it does neither. It explains the 'what' and 'why' but is silent on parameters and response formats, making it incomplete for effective use. The description would need parameter explanations or output details to be considered adequate for this complexity.

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% – no property has a description. The tool description does not mention any parameter names or meanings; it only vaguely refers to 'credentials' in relation to the platform, not the specific schema fields. Since schema coverage is low, the description should have compensated but does not, leaving users to guess at parameters like login_cpf or pkcs12_cert.

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's function as querying the official 'Extrato Geral (NCP) nada consta' from DETRAN PE. It uses a specific verb ('consulta') and resource, and differentiates from generic sibling tools by specifying the official data source and payment model. This makes its purpose unambiguous.

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: it queries official Brazilian sources, is hosted by the platform, requires prepaid credit, and mandates LGPD compliance. However, it does not explicitly state when to use this tool over alternatives or include exclusion criteria, so it stops short of a 4 or 5. The context is useful but lacks comparative guidance.

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