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

Annotations already mark the tool as read-only, idempotent, and non-destructive. The description adds useful context beyond that: prepaid credit is consumed, no platform credentials are needed, the data is non-confidential, and the client is responsible for LGPD compliance. It does not mention response behavior, but the annotations are clear about potential outcomes.

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 purpose is front-loaded and the description remains concise, with only a few sentences. Some redundancy exists between 'consulta em fonte oficial' and 'informação de fontes e órgãos oficiais', but the extra legal/pricing context is useful.

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 13-parameter tool with no output schema and no schema descriptions, the description is not complete enough for reliable invocation. It explains the commercial and legal context, but it does not cover the query semantics, expected output, or criteria for selecting the right combination of parameters.

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 input schema has 13 parameters but 0% schema description coverage, and the description does not explain any of the possible parameters such as cpf, numero_processo, or instancia. The agent receives no guidance about what those fields mean, what is needed, or exactly which filters can be combined.

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 identifies the resource (TJPR court process) and the action (consulta/consultation) against an official source. While it is not a full imperative sentence, the first clause is enough to distinguish the tool from the generic 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 implies when to use the tool: to retrieve official TJPR case information, without platform credentials, and with prepaid credit. However, it does not explicitly describe when not to use it nor name alternative tools for different scenarios.

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