breakpoint_set_exception

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

No annotations provided, so description must disclose behavioral traits. It reveals that passing empty array clears filters, but does not specify if it replaces or adds to existing filters, does not mention required debugger state, side effects, or error conditions. For a mutation tool with no annotations, this is insufficient.

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 deliver purpose, clearing behavior, and examples with zero wasted words. Front-loaded with primary action and critical usage hint.

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?

Tool is simple (one param, no output schema) but lacks important context: effect on existing filters, whether debugger must be attached, and return behavior. Adequate for basic use but incomplete for robust agent decision-making.

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 has 100% coverage with param description, but the tool description adds concrete filter examples ('all', 'user-unhandled'), which go beyond schema and help an AI agent use the parameter correctly.

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 sets exception breakpoint filters, with verb 'set' and resource 'exception breakpoint filters'. It distinguishes from sibling breakpoint_set tools by focusing on exception filters, and provides an example of clearing with empty array.

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?

Includes explicit usage guide: 'Pass [] to clear.' Also lists common filters 'all' and 'user-unhandled'. While it doesn't explicitly exclude alternatives, the sibling names (breakpoint_set, breakpoint_set_data, etc.) make the purpose clear. Lacks when-not guidance but sufficient for selection.

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