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

Annotations already provide read-only and idempotent hints. The description adds valuable behavioral context beyond annotations: hosted by the platform, no platform credentials required, pay-per-query with pre-paid credits, official/non-confidential data source, and LGPD data-controller responsibilities. No contradiction with annotations.

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 reasonably concise and front-loaded with the primary purpose. The additional sentences about payment, official sourcing, and LGPD add useful context, though some legal boilerplate could be trimmed without losing core invocation guidance.

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 tool has no output schema and the description does not explain return values or parameter semantics. While it covers data source, payment, and legal context, it fails to describe the 'grau' parameter or expected 'numero_processo' format, leaving a significant gap for correct invocation.

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 offers no explanation of the parameters 'grau' or 'numero_processo'. It does not compensate for the schema's lack of descriptions, leaving the agent without guidance on required formats or possible 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 it performs procedural consultation for TRT24 from official sources, with a specific verb ('Consulta') and resource ('Processo'). It also differentiates itself from the sibling platform tools, which are generic utilities like authenticate 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 gives clear context about when to use the tool: for consulting official Brazilian public court data, with pre-paid credits and no platform credentials needed. It does not explicitly name alternatives or exclusion conditions, but sibling tools are unrelated, making the intended use fairly unambiguous.

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