trigger_pipeline

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

Annotations are absent, so the description carries the full burden for behavioral disclosure. It does not mention that triggering a pipeline is a mutating action, may cause builds to run, require specific permissions, or have other side effects. Only the basic action is stated, which is insufficient for a write operation.

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 concise: a one-sentence summary followed by a structured parameter list. No unnecessary words or repetition, and the format is easily parseable by an agent.

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?

The description adequately covers purpose and parameters, and an output schema exists, so return details are not needed. However, it lacks usage guidelines and behavioral transparency, making it incomplete for a mutation tool. Overall, it is a minimal but functional description.

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 Args section provides clear, meaningful descriptions for all four parameters, compensating fully for the 0% schema description coverage. It explains branch, custom_pattern (including optionality), workspace, and repo, adding value beyond the schema's bare titles and defaults.

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: 'Trigger a pipeline run for a branch.' This uses a specific verb and resource, and it distinguishes this tool from sibling pipeline tools like list_pipelines, stop_pipeline, and pipeline_steps by focusing on the trigger action.

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, nor are there any prerequisites or exclusions. The description only states the core action, leaving the agent to infer usage context from the tool name and sibling list without explicit direction.

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