Run pipeline by name

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

No annotations provided, so description must disclose behavioral traits. It states the tool searches by partial name and queues a run. However, it does not clarify behavior for multiple matches, whether the run is async, or error conditions like insufficient permissions.

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?

Description is 4 sentences, front-loaded with core purpose. Every sentence adds unique value: purpose, usage examples, search-and-run mechanism, and advice to skip list_pipelines. No wasted 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 tool's complexity (3 parameters, no output schema, no annotations), the description covers key aspects: search-and-run workflow, language examples, and workflow optimization. Missing details on multiple matches and async behavior, but still adequate.

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?

Input schema has 100% description coverage for all 3 parameters. The description adds only the notion of 'partial name' for pipelineName, which is marginally more specific than the schema. No added value for other parameters.

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?

Description clearly states the tool finds a pipeline by name and runs it. The verb 'run' and resource 'pipeline' are explicit. It distinguishes itself from the sibling 'run_pipeline' by using name-based search rather than requiring an ID.

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?

Provides explicit when-to-use examples (e.g., 'run pipeline X', 'trigger X') and tells users not to call list_pipelines first. However, it does not mention when to prefer the sibling tool 'run_pipeline' (e.g., when pipeline ID is known).

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