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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context beyond annotations: the prepaid credit/payment model, lack of platform credentials, official non-confidential nature of the data, and LGPD data-controller responsibility. No contradiction with annotations exists.

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 front-loaded with the core purpose and then adds relevant legal/commercial caveats in four concise sentences. No sentence is entirely wasted, though the LGPD clause could be seen as boilerplate.

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 10 optional parameters, no output schema, and no parameter-level descriptions, the tool is operationally complex, but the description omits query construction semantics, minimum required fields, pagination behavior, and result handling. It covers legal and payment context but not enough operational detail for reliable use.

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 explain any of the 10 parameters such as rg, cpf, oab, numero_processo, or pagina. It provides no guidance on which identifier is preferred, whether at least one is required, or how the parameters relate to each other, leaving the agent without enough semantic grounding.

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: 'Tribunal TJSP: Processos do 2º Grau, consulta em fonte oficial.' This names a specific verb (consulta), resource (TJSP 2º Grau processes), and scope (official source). It is clearly distinguishable from the generic sibling tools such as authenticate, marketplace, and report_bug.

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 gives useful operational context: no platform credentials are needed, queries are paid with prepaid credit, the data is the same publicly available to citizens, and the client is responsible for LGPD compliance. It does not explicitly name exclusions or alternatives, but the sibling tools are system-level and not competing consultation tools.

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