gitlab-ci-mcp

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, covering safety and idempotency. The description adds useful behavioral context about pagination (implied through examples), recursive traversal behavior, and the distinction between listing vs. content retrieval, which goes beyond what annotations provide.

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 perfectly structured with a clear purpose statement followed by practical examples and a specific exclusion. Every sentence earns its place, with no wasted words. The information is front-loaded with the core functionality stated first.

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 has comprehensive annotations, 100% schema coverage, and an output schema (implied by context signals), the description provides exactly what's needed. It explains the tool's purpose, gives usage examples, distinguishes from alternatives, and provides behavioral context - all without duplicating structured data.

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 all parameters are well-documented in the schema. The description adds minimal parameter semantics beyond the schema - it mentions 'recursive=True' in an example and implies path usage, but doesn't provide additional parameter meaning. This meets the baseline for high schema coverage.

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 tool's purpose with specific verb ('List') and resource ('files and directories at a given path in the repository'). It distinguishes from sibling gitlab_get_file by explicitly stating 'Don't use for full-text content — use gitlab_get_file for that,' showing clear 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 usage guidance with three examples showing different scenarios, including when to use the tool (top-level files, recursive filtering) and when not to use it (full-text content). It names the alternative tool (gitlab_get_file) for content retrieval, giving clear context for tool selection.

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