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

Annotations already signal read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond annotations: the tool is hosted by the platform, requires prepaid credit, accesses citizen-available official data, and imposes LGPD controller responsibilities on the client. No contradiction with annotations exists.

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 compact and front-loaded with the core purpose. The additional sentences about payment, official sources, and LGPD are relevant operational context, though the final clause is somewhat legal boilerplate and not strictly necessary for tool invocation.

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 six optional parameters and no output schema, the description is not complete enough for reliable invocation: it offers no parameter semantics, expected combinations, or result expectations. Annotations cover safety traits, but the actual query contract remains ambiguous.

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%, yet the description provides no guidance about any of the six parameters (cpf, oab, cnpj, parte, advogado, processo). It does not clarify valid formats, required combinations, or which identifier should be supplied for a query, leaving the agent to guess.

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 verb and resource: consult ('consulta') TRF1 process data in an official source. It also distinguishes itself from the sibling platform-level tools (authenticate, connect, marketplace, etc.) by explicitly naming the legal domain and query action.

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 queries official public data, requires no platform credentials, and involves prepaid per-query credit. It does not explicitly name alternatives or when-not-to-use scenarios, but the sibling list makes those alternatives obvious and unrelated, so the context is clear.

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