retry_pipeline

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

No annotations are present. The description claims 'retry' but does not disclose what happens (e.g., creates a new pipeline, modifies the existing one, or triggers a rerun). Behavioral effects are unclear.

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 with no wasted words. However, the description is overly brief and could be expanded with more context without losing conciseness.

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?

No output schema is provided. The description lacks any indication of return value or behavior upon success/failure. For a simple tool, it is minimally adequate but could be more complete.

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 coverage is 100% for the two parameters. The description adds no additional meaning beyond what the schema provides. Baseline score of 3 applies.

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 'Retry a failed pipeline' clearly states the action (retry) and the resource (a failed pipeline). It distinguishes this tool from siblings like 'create_pipeline' (creates new) and 'cancel_pipeline' (cancels).

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. It does not specify that the pipeline must be in a failed state, nor does it contrast with 'create_pipeline' for initiating new runs.

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