Create Pipeline

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

The annotations indicate readOnlyHint=false and destructiveHint=false, so the tool is mutating but not destructive. The description adds no additional behavioral details (e.g., what side effects occur, required permissions, or rate limits). It merely states the obvious action.

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?

At only four words, the description is overly terse. While concise, it sacrifices useful information. It lacks structure and does not front-load important details beyond the basic action.

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 complexity of creating a pipeline (multiple parameters, no output schema), the description is severely incomplete. It does not explain return values, prerequisites, or the expected behavior when parameters are omitted. The agent would struggle to invoke this 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 schema documentation coverage is 0%, meaning no parameters are described in the schema. The description fails to compensate: it does not explain what 'ref', 'inputs', 'variables', or 'project_id' mean or how to use them. For a tool with 4 parameters and 0% coverage, this is a critical gap.

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 'Trigger a new pipeline' uses a specific verb and resource, clearly indicating the action. However, it does not differentiate from sibling tools like gitlab_retry_pipeline or gitlab_cancel_pipeline, which are also pipeline-related but serve different purposes.

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. Siblings include gitlab_retry_pipeline, gitlab_cancel_pipeline, and gitlab_list_pipelines, but the description does not help the agent choose between them.

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