gitlab-ci-mcp

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds valuable behavioral context beyond annotations by specifying the return content ('full timing details', 'status, ref, source, durations, timestamps') and providing concrete examples of how to interpret specific fields for troubleshooting. However, it doesn't mention rate limits or authentication requirements.

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 with a clear purpose statement, usage guidance, return details, and practical examples. Every sentence adds value, and the information is front-loaded with the most important details first. The bullet-point examples are concise and directly relevant to common use cases.

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 comprehensive annotations (readOnly, non-destructive, idempotent, openWorld), 100% schema description coverage, and the presence of an output schema, the description provides excellent contextual completeness. It explains when to use the tool, what it returns, how to interpret results, and distinguishes it from alternatives—exactly what's needed beyond the structured fields.

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%, with both parameters well-documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema, so it meets the baseline of 3. The description focuses on tool usage rather than parameter details, which is appropriate given the comprehensive schema documentation.

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 specific action ('Get a single pipeline with full timing details'), distinguishes it from the sibling 'gitlab_list_pipelines' (which returns summaries), and explicitly differentiates it from 'gitlab_get_pipeline_jobs' for individual job details. This provides a precise verb+resource+scope combination with clear sibling differentiation.

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 this tool ('Useful right after gitlab_list_pipelines'), when not to use it ('Don't use to see individual jobs'), and names the alternative tool for that purpose ('use gitlab_get_pipeline_jobs'). It also includes practical examples that illustrate appropriate use cases.

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