list_groups

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds a genuinely useful operational fact beyond them: the upstream is read-only and groups can only be managed through the Gryzzly UI, so no create/update tool exists. It does not cover pagination behavior or result shape, but the output schema handles returns.

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?

Two short sentences with no filler. The purpose is front-loaded and the read-only constraint follows immediately, so nothing is wasted.

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 zero-required-parameter list tool with a full schema and an output schema, the description is largely sufficient: identity, domain meaning, and the read-only upstream constraint are all covered. It stops short of routing the agent among the many list_* siblings, which is the remaining gap.

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 100% and every one of the five parameters (ids, limit, query, offset, set_ids) is documented in the schema itself. The description adds no filtering, pagination, or format detail beyond that, so the baseline 3 applies.

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?

States a clear verb (List) and resource (groups) and adds domain meaning by explaining that groups are the user groupings to which Gryzzly assigns projects and rates. It does not, however, distinguish itself from near-siblings like list_groupsets or get_group, so an agent must infer the boundary.

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 no explicit when-to-use guidance, no conditions for choosing this over get_group, list_groupsets, or list_users, and no prerequisites. The only directional hint is that writes must happen in the Gryzzly interface, which is behavioral rather than usage-selection guidance.

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