Pause debugger

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

With no annotations, the description carries the full behavioral disclosure burden. It reveals that the pause occurs at the next JavaScript statement and that it is a request, but it does not mention prerequisites like an active session, side effects, or whether the tool blocks or resolves.

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 one short, grammatically clear sentence front-loaded with the action. No word is wasted, though it sacrifices information that would be necessary for full usability.

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 debugger control tool with two parameters and no annotations or output schema, the description is under-specified. It fails to explain parameter roles, required session context, or interaction with other debugger tools, making it incomplete for reliable invocation.

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 description coverage is 0% and the description does not mention either sessionId or targetSessionId. An agent cannot infer what session these parameters refer to or how targetSessionId differs from sessionId.

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 uses a specific verb 'Request a pause' and identifies the exact resource/action: the next JavaScript statement. It clearly differentiates from sibling tools like debugger_resume, debugger_step, and debugger_run_to_location by focusing on pausing.

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?

No guidance is provided on when to use this tool versus alternatives such as debugger_step or debugger_run_to_location. The description simply states the action, leaving the agent to infer when pausing is appropriate.

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