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

Beyond the annotations, it discloses cost implications (prepaid credits), data sensitivity (not confidential), and legal responsibility under LGPD. These are significant behavioral aspects not covered by the 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 concise, using a few sentences to convey essential information. Each sentence adds relevant context (official source, cost, data sensitivity) without excessive verbosity.

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 covers key operational aspects: official source, cost model, data confidentiality, and legal compliance. It does not mention response format, but given the absence of an output schema, this is acceptable.

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 description provides no explanation for the parameters 'grau' or 'numero_processo'. It does not clarify their meaning, format, or acceptable values, leaving users without guidance on how to construct a request.

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 is for procedural consultation at TRT4, using official sources. It distinguishes from sibling tools like authentication or marketplace by specifying the domain and function.

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?

It implies usage when needing to query a TRT4 process and mentions the requirement of prepaid credits, which serves as a usage guideline. However, it does not explicitly contrast with alternative tools or provide detailed scenarios.

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