forcePause

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

The description discloses the primary behavior (forcing a pause) but does not mention potential side effects like whether a debugger must be attached or if the pause is persistent. Since annotations are absent, some additional detail could be provided.

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?

The description is concise, with the action stated first and the use case in the second sentence. It is well-organized and front-loaded.

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?

The description is adequate for the tool's simplicity, but it omits any mention of error cases or prerequisites (e.g., need for an active debugging session). This is 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 tool has no parameters, and the description correctly does not attempt to explain any. Schema coverage is complete, so no additional parameter info is needed.

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 the tool forces the debugger to pause at the next JavaScript statement, with a specific verb and resource. It distinguishes itself from setBreakpoint by noting when it is useful.

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?

Explicit guidance is given: useful when source code cannot be modified and setBreakpoint is not feasible, implying when not to use it.

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