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

With no annotations, the description carries full behavioral disclosure and does so well: it states that existing runs continue, no new runs start, and the operation is reversible via workflows_resume. This is meaningful behavioral detail beyond a simple 'pause' label.

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 short sentences deliver the purpose, the key behavioral distinction, and the reversal path with zero filler. The most important information is front-loaded and every sentence 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 simple one-parameter tool, the description is nearly complete: it explains the immediate effect, the boundary between existing and future runs, and how to undo the operation. It does not mention idempotency or result/error behavior, but the low complexity and clear scope make this a minor gap.

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?

The schema already covers the single parameter fully with 100% coverage, including its type and meaning ('Workflow UUID'). The description does not need to repeat this, and it adds no extra parameter-level nuance, so the baseline score of 3 is appropriate.

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 identifies the action (pause) and resource (workflow), and explains the operational effect: it stops firing on its trigger. It also distinguishes itself from the related workflows_resume sibling without needing to open either schema.

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 description gives clear context for when to use this tool: stop future workflow firings while letting existing runs continue. It also points to workflows_resume as the reversal alternative, though it does not explicitly mention when not to use it, such as preferring workflows_delete for permanent removal.

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