list_groupsets

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 real context beyond that: groupsets are managed upstream in the Gryzzly web app, so no write path exists, and an empty result is an empty list rather than an error. It stops short of describing pagination behaviour or result ordering, but the safety profile is well covered.

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?

Three sentences, front-loaded with the definition, then usage, then behavioural constraints. Every sentence carries information the agent needs; nothing is padding.

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?

An output schema exists, so return-shape detail is not required here. The description covers the domain model, the read-only constraint, the empty-result semantics, and routing to siblings, which is everything needed to call a five-parameter list tool correctly.

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%, so all five filters (ids, limit, query, offset, set_ids) are already documented in the schema. The description adds no filter syntax, pagination interaction, or default-value guidance, 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 specific verb and resource ('List groupsets') and immediately defines the domain concept ('the families user groups belong to ... holds groups such as teams or sites'). It also names the sibling it is not (get_groupset for a single one), so an agent can distinguish it from list_groups and get_groupset without opening a schema.

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?

Gives explicit sequencing advice ('use it to understand how the team is organised before reading list_groups') and points to the alternative for the single-item case ('use get_groupset for one groupset'). Both when-to-use and the alternative are spelled out rather than inferred.

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