List groups

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

Annotations already state readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds the context that the list is scoped by token visibility, which is useful. However, it does not disclose pagination behavior or return format, so it provides only marginal additional behavioral context beyond annotations.

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 concise sentence with no filler. It front-loads the core purpose immediately and is appropriately sized for the tool's simplicity.

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 the read-only annotation, the tool has 7 parameters including pagination and filtering options. The description lacks any mention of pagination, result limits, or filtering behavior, which are necessary for an agent to use the tool effectively. The one-line description is too sparse for the tool's complexity.

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 57%, meaning three parameters (owned, search, top_level_only) lack descriptions. The tool description does not explain any parameter semantics or compensate for this gap. With 7 parameters and no parameter-related info in the description, the agent must rely solely on the partial schema.

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 'Lists groups visible to the token' clearly identifies the action (lists) and resource (groups), with the scope being groups the token can access. It distinguishes from get_group (single group) but does not explicitly differentiate from sibling list tools like list_group_projects, so it stops short of a 5.

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 guidance on when to use this tool versus alternatives, nor does it mention any exclusions or typical use cases. It only states the basic function, leaving the agent to infer when listing groups is appropriate.

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