pause_execution

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

Annotations declare idempotentHint=true and openWorldHint=false. Description adds crucial behavioral info: that it returns immediately and does not wait for a stopped event, unlike step tools. This goes beyond annotations, though annotations already indicate it's safe to retry.

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?

Four sentences, each earning its place. No fluff. Front-loaded with the core action. Ideal 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?

For a simple tool with one optional param and no output schema, the description covers the main behavioral aspects: required state, non-blocking nature, recommended follow-up, and escape hatch. Minor missing detail about thread_id, but overall sufficient.

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% and the description does not explain the thread_id parameter. While the parameter name and type are self-evident, the description fails to add context (e.g., what happens when null). This is a gap given low coverage.

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 states 'Pause program execution' with a specific verb and resource. It distinguishes itself from sibling step/continue tools by noting it returns immediately and does not block. The required state 'RUNNING' is also specified.

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 states when to use: 'State: RUNNING required.' and suggests using get_call_stack() after pause. Contrasts with continue/step tools and provides an escape hatch reference, offering clear when-to-use and when-not guidance.

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