pause_execution

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

Annotations already declare it non-readOnly, non-idempotent, and non-destructive; the description adds meaningful detail beyond them: the pause takes effect at a stage boundary rather than immediately, and the action is reversible via resume_execution. It doesn't state authorization requirements or behavior when the execution isn't mid-pipeline.

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?

Three tight sentences with the core action front-loaded and no redundancy. The closing return-value sentence is mildly useful given there is no output schema, though it is close to filler.

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 one-parameter tool with annotations covering the safety profile, the description is nearly complete: it explains scope, reversibility, and the confirmation return. A minor gap is what happens if the execution is not currently running or already paused.

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% with a single well-documented execution_id parameter, so the schema carries the load. The description adds no format or sourcing detail beyond what the schema provides; baseline 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?

States a specific verb ('Pause'), resource ('running pipeline execution'), and granularity ('at the current stage boundary'), which cleanly separates it from sibling tools like cancel_execution, resume_execution, and restart_stage.

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?

Gives a concrete use case (temporarily halt a deployment for manual review) and points to the follow-up tool, resume_execution. It does not contrast against cancel_execution, so the agent must infer when pausing is preferable to cancelling.

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