Pause business execution

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. Description adds 'while waiting' context but lacks details on state changes, reversibility, or blocking behavior. Adds some value beyond structured fields.

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?

One sentence, 14 words, front-loaded with essential purpose. No wasted words. Efficiently conveys core action and condition.

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?

Provides basic purpose but lacks context for selection among siblings, prerequisites, or handling of repeated pauses. Output schema exists but return behavior is not described. Minimal but adequate for a simple tool.

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 0%, yet description provides no explanation for 'reason' or 'message' parameters. Fails to compensate for missing schema documentation. Agent cannot infer parameter semantics from description.

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?

Clearly states verb 'Pause', resource 'current business action', and condition 'while waiting for a user, dependency, or external system'. Effectively distinguishes from siblings like flow.abort (terminate), flow.finish (complete), flow.resume (continue), flow.rewind (go back).

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?

Explicitly mentions when to use (while waiting). Provides clear context but does not specify when not to use or name alternatives beyond sibling list. Implies usage through condition.

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