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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'complete data' and bulk execution context, but it does not disclose result shape, error behavior, or any response details. 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 only two sentences: the first front-loads the core purpose, and the second adds bulk behavior. No filler or redundant restating of the tool name.

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?

With no output schema and no parameter descriptions, the definition should provide more context about the return payload and the role of 'query'. It states 'dados completos' and bulk support, which is enough for a simple get-by-ID tool, but the unresolved query parameter keeps it from being fully complete.

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 input schema has 0% description coverage, but the description partially compensates by explaining processo_id ('by ID') and processo_ids ('bulk support'). However, the 'query' parameter is left completely unexplained, and the relationship between required processo_id and optional processo_ids is ambiguous.

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 'Busca um processo por ID (dados completos)' uses a specific verb ('busca'), names the resource ('processo'), and clearly specifies retrieval by ID with full data. This differentiates it from siblings like easyjur_list_processos and other easyjur_get_* tools.

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?

'Bulk support: accepts processo_ids for batched execution' gives concrete guidance on when to use the bulk parameter. It does not explicitly exclude alternatives, but the get-by-ID vs. list distinction is clear from the name and description.

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