gitlab-ci-mcp

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description reinforces this with 'Read-only and idempotent' but adds valuable context about the return format ('Returns PipelinesListOutput... The tool result additionally carries a markdown table in its text content'), which isn't covered by annotations. It doesn't contradict 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 efficiently structured: purpose statement first, usage guidelines second, return format third, and examples last. Every sentence adds value—no fluff. It's appropriately sized for a tool with 6 parameters and rich functionality.

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 the tool's complexity (6 parameters, pagination, filtering), the description is complete. It covers purpose, usage, behavioral traits (reinforcing annotations), and provides concrete examples. With an output schema present, it appropriately explains the return structure without redundancy. It addresses all necessary context for an agent to use the tool effectively.

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 schema fully documents parameters. The description adds practical meaning through examples that show how parameters combine in real use cases (e.g., 'status="failed", ref="master"' for triage), enhancing understanding beyond the schema's technical definitions.

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 clearly states the verb ('List') and resource ('recent pipelines of a project') with specific ordering ('newest first'). It distinguishes from siblings like 'gitlab_get_pipeline' by emphasizing listing vs. getting a specific pipeline, and from other list tools by focusing on pipelines specifically.

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 provides explicit guidance on when to use ('for triage, release readiness checks, or feeding pipeline IDs into follow-up calls') and when not to use ('Don't use when you have a specific pipeline ID — use gitlab_get_pipeline instead'). It names a clear alternative tool for specific cases.

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