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

Read-only and idempotent behaviors are already in the annotations, but the description adds meaningful operational and legal context: prepaid billing, official-source data, non-confidential information, and LGPD responsibility. This supplements the annotation flags with important usage constraints.

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 main purpose is front-loaded, but the description is somewhat repetitive: 'consulta em fonte oficial' and 'Consulta informação de fontes e órgãos oficiais' say similar things. The LGPD clause is useful but adds length, so the text is moderately concise rather than tightly written.

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?

No output schema exists and parameter coverage is 0%, so the description must provide enough operational detail to complete a call successfully. It addresses commercial and legal context but does not explain the input fields, required 'numero_pedido', or what kind of certidão response will be returned.

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%, yet the description does not explain any of the four parameters (cpf, cnpj, pedido_data, numero_pedido) or mention required fields. There is no guidance on how to construct a valid request, so parameter semantics are essentially absent.

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 begins with 'Tribunal TJSP: Visualizar Certidão, consulta em fonte oficial', clearly identifying a specific verb, resource, and court context. This strongly distinguishes the tool from the unrelated siblings such as authenticate, connect, and marketplace.

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 some usage context: it is platform hosted, requires no platform credentials, and charges per consultation using prepaid credit. However, it does not explicitly state when to use this tool versus alternatives, or when not to use it, leaving the guidance incomplete.

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