Control pipeline and jobs

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

The annotation destructiveHint=false contradicts the description's mention of 'cancels pipeline', which is a destructive action. The description does not clarify behavioral traits like permissions, idempotency, or side effects 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 short, but it is a list of actions without structure. It could be improved by grouping actions or adding context, but it is not overly verbose.

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 6 parameters and multiple actions, the description is insufficient. It does not explain return values (no output schema) or how to combine parameters for each action, leaving significant gaps.

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 description does not add any meaning beyond the input schema. It fails to explain how parameters relate to actions (e.g., which parameters are needed for 'play' vs 'retry'). Schema coverage is 50%, but the description offers no compensation.

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 lists the tool's actions (list jobs, play, retry, cancel), indicating it controls pipelines and jobs. However, it does not distinguish from sibling tools like gitlab_get_pipeline or gitlab_list_pipelines, lacking specificity about what makes this tool unique.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, forbidden combinations, or scenarios where another tool would be better.

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