Pause on exceptions

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

With no annotations, the description carries the full burden, and it does disclose a genuine behavioral trait not present in the schema: the default mode of 'uncaught'. However, it omits whether a call replaces or adds to existing exception-breakpoint state, whether it affects all scripts, and what happens to a currently paused session.

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 short sentences with the purpose front-loaded and the default surfaced immediately after. No filler or redundancy.

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 single-parameter control tool with no output schema or annotations, the description covers purpose and default but leaves gaps: per-enum semantics and the replace-vs-accumulate behavior of repeated calls. Adequate but not complete.

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?

There is one enum parameter with 0% schema description coverage, so the description must compensate. It explains the parameter's axis (pause on exception thrown) and reveals the default value 'uncaught', which the schema enum alone does not convey, but it never spells out what 'none' versus 'all' versus 'uncaught' each mean beyond the obvious naming.

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 ('Control') and resource ('whether the debugger pauses when an exception is thrown'), which is clearly distinguishable from the sibling set_breakpoint (line breakpoints). It does not explicitly name or contrast itself with that sibling, so it falls short of a 5.

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?

The note 'Default is uncaught' gives implied usage context, but there is no explicit when-to-use guidance, no statement of when to prefer this over set_breakpoint, and no mention of prerequisites or side effects on running sessions.

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