list_pipeline_trigger_jobs

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

No annotations are provided, so the description carries the full behavioral burden. 'List' clearly signals a read-only operation, and the scoping to a specific pipeline is transparent. However, it does not disclose pagination behavior, response format, or clarify that this operation does not actually trigger downstream pipelines despite the 'trigger' terminology.

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 a single, front-loaded sentence with no filler. Every phrase earns its place: the verb, the resource, the parenthetical clarification, and the scope qualifier.

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 is adequate for a simple filtered-list tool, especially with the input schema covering all five parameters. Still, there is no output schema or annotations, and the description does not mention the scope filter or pagination, leaving some context gaps for an agent deciding how to invoke it.

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 baseline is 3. The description adds minimal semantic value beyond the schema—it reinforces that the tool targets a specific pipeline, but it does not elaborate on scope, page, per_page, or project_id/pipeline_id usage.

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 opens with a specific verb ('List'), identifies the resource ('trigger jobs (bridges)'), and scopes it clearly to a specific pipeline that triggers downstream pipelines. This distinguishes it from sibling tools like list_pipeline_jobs, which handles regular pipeline jobs.

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 intended use case is implied: call this when you need bridge/trigger jobs for a specific pipeline. However, the description does not explicitly say when to prefer this over list_pipeline_jobs or other pipeline-related siblings, nor does it mention any exclusions.

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