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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds valuable context: it's hosted by the platform, requires prepaid credit, and clarifies data privacy (LGPD) and that the client is the data controller. This goes beyond annotations and provides important operational and legal context.

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 paragraph, reasonably concise, and front-loaded with the core purpose. It includes necessary legal and payment context without excessive verbosity. However, it could be slightly more structured, but overall it's efficient.

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 the tool's complexity (10 optional parameters, no output schema, no parameter descriptions), the description is incomplete. It covers the purpose, payment, and legal aspects, but lacks guidance on parameter usage, expected results, or any limitations. The annotations help with safety, but the description doesn't fully compensate for the lack of schema documentation.

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. The parameter names are somewhat self-explanatory (cpf, oab, cnpj, numero_processo, etc.), but the description provides no guidance on how to use them, which combinations are valid, or any format requirements. With 10 parameters and no coverage, the description should compensate but doesn't.

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: consulting process information from the official TJRJ source. It specifies the resource (processo) and the court (TJRJ), and distinguishes it from generic tools by mentioning the official source and payment model. However, it doesn't explicitly differentiate from sibling tools, though siblings are mostly unrelated (auth, marketplace, etc.).

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 implies usage context: it's for consulting official Brazilian court data, with a prepaid credit model. It mentions that the data is the same available to citizens and not confidential, which gives some context. However, it doesn't explicitly state when to use this tool vs alternatives, nor does it provide exclusions or prerequisites beyond payment.

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