debuggerDeleteBreakpoints

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Deletes breakpoints' implies a destructive mutation, but provides no information about permissions required, whether deletion is permanent or reversible, what happens to associated debugging state, error conditions, or response format. For a destructive operation with zero annotation coverage, this complete lack of behavioral context is inadequate and potentially misleading about the tool's impact.

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?

While technically concise with just two words, this description is under-specified rather than efficiently informative. It fails to provide necessary context that would help an agent understand when and how to use the tool. True conciseness balances brevity with completeness - here the extreme brevity comes at the cost of leaving critical information gaps that would require the agent to make assumptions or trial-and-error invocations.

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 destructive debugging tool with 6 parameters, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what constitutes a successful deletion, what errors might occur, how breakpoints are identified, or the debugging context required. The agent would have insufficient information to use this tool correctly without resorting to experimentation or external documentation, creating significant risk for incorrect usage in a debugging environment.

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 100%, with all 6 parameters documented in the schema itself. The description adds no parameter information beyond what's already in the structured schema. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description. The description doesn't compensate or add value, but doesn't need to since the schema already provides complete parameter documentation.

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 'Deletes breakpoints' is a tautology that essentially restates the tool name 'debuggerDeleteBreakpoints'. It provides the verb 'deletes' and resource 'breakpoints', but doesn't specify scope (e.g., all breakpoints, specific ones), context (debugging session), or distinguish it from sibling tools like 'debuggerSetBreakpoints' or 'debuggerDeleteListener'. This minimal statement fails to differentiate the tool's specific purpose within the debugging context.

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 description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., must have active debugging session), when it's appropriate (e.g., to clean up after debugging), or what happens if used incorrectly. With sibling tools like 'debuggerSetBreakpoints' and 'debuggerDeleteListener' in the same domain, the lack of differentiation leaves the agent guessing about the appropriate context for this deletion operation.

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