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 the bulk behavioral trait ('accepts grupo_ids for batched execution'), which is useful context beyond the annotations. However, it omits other behavioral details such as pagination behavior, return type, or any side effects, though read-only nature is established.

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 with no filler. It front-loads the core purpose and adds a single relevant note on bulk support. Every word earns its place, and the structure is easily scannable.

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?

Despite having a nested query parameter, 5 parameters, and no output schema, the description is minimal. It does not explain the query object, pagination semantics, or what the response contains. While annotations cover safety, the tool's usage complexity demands more context for correct invocation. The description is incomplete for an agent to operate effectively without external 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%, so the description must compensate for parameter meaning. It only addresses grupo_ids (bulk support) and implicitly grupo_id from the tool name, but does not explain query (a nested object), page, or page_size. Given the blank schema, the description fails to provide adequate semantics for most parameters, leaving the agent to guess their format and usage.

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: 'Lista processos de um grupo' (lists processes of a group). This is a specific verb+resource combination that distinguishes it from sibling tools like easyjur_list_processos (which lacks the group filter) and other entity-specific group list 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?

The description does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. The only extra hint is the bulk support note, but it does not explain the distinction between singular (grupo_id) and plural (grupo_ids) usage. With many similar sibling list tools, clearer usage guidance is needed.

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