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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds complementary behavioral context: no platform credentials, prepaid credit billing, official public data, non-confidential scope, and LGPD data-controller responsibility. This meaningfully enhances what annotations provide.

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 moderate length with a front-loaded purpose statement followed by payment, data-source, and LGPD context. Each sentence adds relevant information, though the LGPD sentence is somewhat boilerplate and could be tightened.

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?

There is no output schema and no mention of return values or result format, while the five-parameter input schema has no descriptions. The description covers legal and commercial context but is incomplete for an agent to know how to structure a valid consultation.

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 mention any of the five parameters (cpf, oab, cnpj, nome_parte, numero_processo), their formats, optionality, or required combinations. With no schema descriptions, the description carries the full burden and completely fails to compensate.

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?

Description states a specific action: 'Processo, consulta em fonte oficial' for Tribunal TRF2, which clearly identifies the resource and operation. It is distinguishable from unrelated siblings such as authenticate and marketplace, though 'Processo' remains somewhat generic without saying it returns case/legal proceeding details.

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 useful context: it is hosted by the platform, requires no platform credentials, and charges prepaid credits per consultation. However, it does not explicitly state when to prefer this tool over alternatives or when not to use it, leaving usage guidance implied rather than explicit.

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