gitlab-ci-mcp

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

Annotations already indicate this is a read-only, non-destructive, idempotent, and open-world operation, covering key behavioral traits. The description adds valuable context beyond annotations by explaining how secret variables are masked (e.g., values replaced with '***'), which is crucial for security and transparency, though it doesn't detail other aspects like pagination or error handling.

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 well-structured and front-loaded, starting with the core purpose, followed by important behavioral details and usage examples. Every sentence adds value, such as the secret masking explanation and explicit usage guidelines, with no wasted words or redundancy.

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 simplicity (one parameter, high schema coverage), rich annotations (read-only, non-destructive, etc.), and the presence of an output schema, the description is complete. It covers purpose, behavioral nuances (secret masking), and usage guidelines, leaving no significant gaps for the agent to understand and invoke the tool correctly.

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?

The input schema has 100% description coverage, fully documenting the single parameter (project_path) with its default behavior and usage. The description does not add any parameter-specific information beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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 ('all CI/CD schedules of a project'), making the purpose specific and unambiguous. It distinguishes this tool from siblings like gitlab_create_schedule, gitlab_delete_schedule, and gitlab_update_schedule by focusing on listing rather than modifying schedules.

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 (e.g., for queries like 'What schedules do we have and are they all active') and when not to use it (e.g., 'Don't use to *run* a schedule now'), with a clear alternative named (gitlab_trigger_pipeline). This helps the agent choose correctly among sibling tools.

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