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 description does not need to repeat safety. It adds the bulk behavior (accepts grupo_ids), which is useful, but does not disclose pagination behavior, return format, or error handling. Given annotation coverage, a 3 is appropriate.

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 extremely concise—two short sentences that are front-loaded with the core purpose and bulk support note. There is no filler or redundancy, making it highly 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 complexity (5 params, no output schema, no param descriptions), this description is incomplete. It fails to explain how to use pagination, query filtering, or page_size, which are essential for a list operation. The bulk support is mentioned but other important parameters are ignored, making the description inadequate for a complete understanding.

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%, so the description must compensate. It only explains grupo_ids for batched execution, leaving page, query, and page_size undocumented. This is insufficient for a 5-parameter tool; the description adds minimal value beyond the schema for most parameters.

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 'Lista oportunidades de um grupo' clearly states the action (list) and the resource (oportunidades) with a specific scope (de um grupo), distinguishing it from the sibling 'easyjur_list_oportunidades' which likely lists all opportunities. The bulk support mention further clarifies an advanced capability.

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 for group-specific opportunity listing but does not explicitly state when to prefer this tool over alternatives like 'easyjur_list_oportunidades' or 'easyjur_list_oportunidades' (which lists all). The bulk support hint provides some context but no exclusions or explicit conditional guidance.

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