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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond the generic act of listing, such as pagination behavior, response shape, or whether query filtering is supported.

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 a single, front-loaded sentence with zero filler: 'Lista grupos (pastas/áreas).' The parenthetical adds useful clarification without increasing length or reducing clarity.

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?

For a tool with three optional parameters, a nested query object, and no output schema, a one-sentence description is insufficient. The annotations mitigate safety concerns, but the agent is still left without guidance on filtering, pagination, or return values.

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 three parameters (page, query, page_size). While 'page' and 'page_size' are somewhat self-explanatory, 'query' is an object with arbitrary properties and is left completely undefined, which the description fails to compensate for.

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 gives a clear verb ('Lista') and resource ('grupos'), with the clarifying parenthetical 'pastas/áreas' helping to identify the domain. It distinguishes from easyjur_get_grupo and other entity-specific list_*_grupo siblings, though it could be more explicit about scope (e.g., all groups vs filtered).

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as easyjur_get_grupo or the other list_*_grupo tools. The intended usage is only implied by the verb 'Lista', so the agent receives no direct support for choosing this over siblings.

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