list_group_merge_requests

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

Annotations already declare readOnlyHint, and the description reinforces it while adding useful error behavior: missing resources, invalid identifiers, insufficient permission, and rate limits return errors. This goes beyond the structured annotations without contradicting them.

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 front-loaded with purpose and overall reasonably sized. However, it contains some redundancy ('read-only' and 'does not mutate') and a generic closing sentence that mentions project_id even though the schema only exposes group_id, which slightly muddies conciseness.

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 complex 27-parameter tool with no output schema, the description covers the key operational context: group/subgroup scope, collection-vs-single selection, read-only safety, error behavior, and identifier format. The remaining gaps are mostly covered by the detailed parameter schema.

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 coverage is 100%, so the schema already documents all 27 parameters. The description adds only generic guidance about numeric IDs/URL-encoded paths and using pagination fields exactly as documented, which is consistent with the schema but adds little new meaning.

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?

Opens with a specific verb-resource-scope statement: 'List merge requests across all projects of a group and its subgroups.' This clearly identifies the operation and distinguishes it from single-resource retrieval tools by instructing to use the corresponding get tool when a single resource is known.

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?

Explicitly says to use this for a collection and to choose the corresponding get tool for a single known resource. It does not name the exact sibling tool (e.g., get_merge_request) or mention project-level list_merge_requests, so the guidance is clear but not fully exhaustive.

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