list_group_projects

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

Annotations already declare readOnlyHint=true, and the description reinforces non-mutation with 'does not mutate GitLab data.' It adds useful error-behavior disclosure: missing resources, invalid identifiers, insufficient permission, and rate limits are returned as errors. This goes beyond what the annotations alone convey.

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, each earning its place: purpose, usage differentiation, and important identifier/pagination behavior. It is front-loaded with the core purpose and contains no filler or repetition.

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?

Given 18 parameters and no output schema, the description still covers the essential decision factors: what the tool lists, when to prefer it, safety profile, error behavior, and identifier format. All parameter details are already in the schema, so nothing critical is missing.

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 the baseline is 3. The description adds meaningful guidance on the accepted form for identifiers ('numeric ID or complete URL-encoded path described by the schema') and directs correct use of pagination fields, which augments the schema's plain property descriptions.

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 begins with a specific verb and resource: 'List projects in a group.' It distinguishes itself from the corresponding get tool explicitly ('choose the corresponding get tool when you already know the single resource to inspect'), making its scope clear relative to siblings.

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?

It provides explicit guidance to use this tool for a collection of resources and to switch to the get tool for a single known resource. It doesn't mention list_projects or other sibling listing tools, but the group scoping in the name and first sentence gives enough context to choose it over general project listing.

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