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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds meaningful behavioral context: the operation is paid via prepaid credits, uses no platform credentials, retrieves only non-confidential citizen-accessible data, and places LGPD-related responsibility on the client. This is substantial useful disclosure beyond the structured hints.

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 four sentences and front-loads the core purpose in the first sentence. The subsequent sentences add relevant context around cost, credentials, data sensitivity, and legal responsibility. There is minor boilerplate in the LGPD clause, but overall the description is efficiently organized.

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 tool is relatively simple and the annotations plus description cover safety, cost, and data sensitivity. However, there is no output schema and the parameter semantics are entirely unaddressed, leaving a noticeable gap for an agent trying to construct a valid request. It is adequate but not complete.

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?

The schema has 0% description coverage and the description never mentions the three parameters (cpf, rip, cnpj). Although the parameter names are somewhat self-explanatory as Brazilian identifiers, there is no guidance on requiredness, mutual exclusivity, or formatting, so the description fails to compensate for the schema's lack of parameter documentation.

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 explicitly states this tool consults 'Dados Cadastrais de Imóvel da União' from an official SEFAZ SPU source. The verb 'consultar' plus the specific resource and official-source context makes the purpose unambiguous and distinguishes it from the unrelated sibling tools.

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 for use: it queries official Brazilian government data, requires no platform credentials, and costs prepaid credits per query. It does not explicitly name alternatives or exclusion conditions, but the official-source and citizen-accessible framing gives sufficient situational guidance.

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