circleci_trigger_pipeline

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

The description states 'trigger' implying a mutation, but with no annotations, it carries full burden. It does not disclose side effects (e.g., cost, build start, multiple triggers), required permissions beyond API key, idempotency, or rate limits. This is insufficient 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?

Single sentence that is front-loaded, compact, and contains no unnecessary words. Every word earns its place.

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?

For a mutation tool with 5 parameters, no output schema, and no annotations, the description is minimal. It does not explain what happens after triggering (e.g., return value, pipeline ID), error cases, or prerequisites. Falls short of completeness given the tool's complexity.

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?

Schema description coverage is 100%, so the schema already documents all parameters. The description redundantly lists 'branch, tag, or parameters' adding no extra meaning. Baseline 3 is appropriate since schema does the heavy lifting, and description adds no further 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 'trigger' and the resource 'CircleCI pipeline', and lists optional parameters (branch, tag, parameters). It distinguishes from sibling tools like circleci_list_pipelines (which lists pipelines) and circleci_get_pipeline (which fetches a single pipeline).

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 such as circleci_list_pipelines or circleci_get_workflow. There is no mention of prerequisites (e.g., CircleCI project setup), when not to use it, or context in which triggering is appropriate.

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