List labels

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which covers the safety profile. The description adds the 'project or group' scope, which provides useful context. However, it does not disclose pagination behavior, fallback to environment variables, or search behavior beyond what the schema already hints at.

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, short sentence that is easy to read and front-loaded with the key scope information. It earns its place but is slightly under-specified, being a noun phrase rather than a complete sentence.

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 there are 7 parameters, no output schema, and minimal annotation detail, the description is too thin. It does not explain the relationship between project and group scoping, how pagination works, or what the response will contain. The agent is left without enough context to reliably invoke the tool in varied scenarios.

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 71%, but the description adds no parameter-level meaning. It loosely maps to project_id/group_id by saying 'project or group', but search and group_id are left undocumented both in the description and the schema. The description does not compensate for the undocumented parameters.

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 title provides the verb 'List' and the description specifies the resource ('labels') and scope ('of a project or group'). This makes the purpose clear, though it does not explicitly differentiate from sibling tools like gitlab_create_label, relying on the verb to imply read-only listing.

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?

No usage guidance is provided. There is no mention of when to use this tool versus alternatives, no prerequisites, and no note about needing to specify either project_id or group_id. The description only states what the tool operates on, leaving the agent to infer appropriate usage.

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