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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable operational context: no platform credentials required, prepaid payment per consultation, data is not confidential, and the client is responsible for LGPD compliance. This goes beyond the annotations without contradicting them.

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 three sentences long and front-loads the core purpose. It adds operational and legal details without excessive verbosity, though it could be slightly more streamlined.

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?

Given the 6 parameters with zero schema description and no output schema, the description is incomplete. It explains the purpose and some operational aspects but omits critical parameter semantics and return-value expectations, making it insufficient for correct invocation.

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 mention any parameters at all. It fails to explain the required 'tipo_certidao' or optional fields like CPF, CNPJ, or parent names, leaving the agent with no guidance on how to fill the parameters 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 the tool performs a 'Nada Consta' consultation from the TJDF court in an official source ('consulta em fonte oficial'). The specific verb 'consultar' and resource 'Nada Consta' distinguish it from sibling tools like authenticate, connect, and marketplace, which are platform-level operations.

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 is for consulting official Brazilian court data, available to citizens, and paid via prepaid credit. It does not explicitly name alternatives or exclusion scenarios, but the context is sufficiently clear for when to use this tool, especially given the unrelated sibling tools.

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