trigger_pipeline

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the tool waits for completion, returns a run ID immediately, or any potential side effects like triggering multiple runs. This is a significant gap for a mutation tool.

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 and front-loaded with the main action. The 'Args:' format is clear and efficient, though slightly verbose due to repeating parameter names. It earns its place without extraneous words.

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 lack of annotations and output schema, the description covers the core purpose and parameter semantics adequately but misses behavioral context (e.g., async nature, response format). It is minimally complete for basic use but leaves gaps for an agent to make informed decisions.

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?

With 0% schema description coverage, the description compensates well by explaining each parameter: project (with default), pipeline_id, and parameters (optional key-value pairs). It adds meaning beyond the schema's default values and type hints, though it does not specify the expected format for parameters (e.g., JSON).

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 starts with 'Trigger a new pipeline run', which is a specific verb+resource combination. It clearly distinguishes from sibling tools like list_pipelines or get_pipeline_runs, which are read-only operations.

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 implies usage when you want to start a pipeline, but it does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites (e.g., obtaining pipeline_id from list_pipelines).

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