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

The description goes beyond the annotations by disclosing that the service is paid (prepaid credits), hosted by the platform, requires no platform credentials, and clarifies data control and LGPD compliance. These are important behavioral traits not covered by the readOnly/idempotent hints, adding substantial value.

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 a single, coherent paragraph that leads with the primary function and then provides operational and legal context. It is not overly verbose, but the information about payment and LGPD could be separated for better scannability. Overall, it is concise and structured adequately for a read-only tool.

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?

The description lacks information about the expected input format (e.g., what 'grau' means) and the nature of the output (e.g., case status, parties, timeline). Since there is no output schema, the description should at least hint at what the response contains, but it does not. This leaves a significant gap in understanding the tool's full behavior.

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 schema has 0% description coverage, and the tool description does not explain the meaning of the parameters 'grau' or 'numero_processo'. The user must infer that 'numero_processo' is the process number, but 'grau' remains undefined. With no compensating explanation, parameter understanding is left entirely to the schema, which itself lacks descriptions, so this is a severe gap.

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 purpose: 'Consulta Processual' (procedural consultation) for TRT22, querying official Brazilian sources. It is distinct from sibling tools like authenticate and connect, which are platform utilities, so there is no ambiguity about its role.

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 context on when to use the tool (to consult official court data) and mentions practical aspects like payment and lack of credentials, but it does not explicitly exclude other tools or name alternatives. Since the siblings are unrelated, the context is clear enough without explicit exclusions.

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