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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuine value beyond this by disclosing the payment model (prepaid credits per consultation), absence of platform credentials, and the public/non-secret nature of the data plus LGPD compliance responsibilities. 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 front-loads the core purpose in its opening phrase, which is good, but roughly a third of the paragraph is LGPD/compliance boilerplate (data controller responsibilities) that does nothing to guide tool invocation. It is one dense paragraph that could say the same in fewer words.

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?

With no output schema present, the description should explain what data the tool returns — it does not. It also leaves the 'grau' parameter unexplained. The tool is simple (2 params, 1 required) and annotations cover safety, so it is not severely incomplete, but the return semantics are a notable gap for an agent deciding how to use results.

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%, so the description must compensate for parameter explanations — it does not. 'numero_processo' is inferable from the tool name, but the optional 'grau' parameter (judicial instance/degree) is never explained anywhere, leaving the agent to guess its meaning or valid values.

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 a specific verb+resource: 'Consulta Processual' (procedural consultation) for TRT12, querying official Brazilian court sources. It distinguishes itself from all sibling tools, which are platform utilities (authenticate, connect, marketplace, report_bug, etc.). Slight deduction for mixing compliance/admin context with the core purpose, though the first phrase is unambiguous.

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 hosted by the platform with a pay-per-query prepaid-credit model, requires no platform credentials, and accesses public (non-confidential) data. However, it never explicitly states when to use this tool versus alternatives or gives any exclusion criteria; the 'when' is only implied by the tool's nature as a court query.

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