pause_execution

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

Annotations only declare idempotent/non-destructive; the description supplies the real behavioral substance: a 2s window, what is returned (the call stack), and that a miss leaves the pause pending rather than failing. That pending-state semantics is exactly the kind of trait annotations cannot express and prevents the agent from retrying unnecessarily.

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?

Two sentences, no filler. The primary behavior and the 2s return condition come first, and the idle-page caveat with the recovery path follows in the same breath.

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 no-parameter tool with no output schema, the description covers what happens, what comes back (call stack), the timing boundary, and the degenerate case. Nothing an agent needs to call it or interpret the result is missing.

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 tool takes zero parameters, so the baseline is 4; there is no parameter semantics to add or omit. The description correctly spends no words on inputs and instead covers behavior.

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) and precise resource/scope (JavaScript execution at the next statement), plus the return value (the call stack). An agent can distinguish this from set_breakpoint or resume_execution without opening any 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?

Explains the crucial conditional case: on an idle page nothing runs, so the pause stays pending until a timer/event/click triggers script, and it routes the agent to get_debugger_state to check. It gives clear context but never explicitly contrasts with set_breakpoint (pause at a chosen line) or step_over, so sibling selection is still partly inferred.

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