Delete ABAP Debugger Breakpoints

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

Beyond the destructiveHint annotation, the description reveals important behavioral details: the no-ids path sends an 'empty full-set sync' that clears server-side breakpoints even if this server no longer remembers them, and 'deleted' counts only what this server knew about. This significantly helps an agent predict side effects and interpret results.

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 well-structured with a lead sentence, labeled args, return shape, examples, and notes. Every section adds operational value, and the most important behavioral caveat about the full-set sync is highlighted with a concrete example.

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?

There is no output schema, but the description provides the return shape '{ deleted, message }' and explains the semantics of 'deleted'. It covers both invocation modes, the side-effect difference between them, and practical guidance for reliable cleanup, so an agent has enough context to invoke it correctly.

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 coverage is 100%, so the baseline is 3. The description adds meaning by explaining that ids are 'structured ids from sap_list_breakpoints / sap_set_breakpoint' and by giving a concrete example id format. It also reinforces the omitting behavior, making the parameter semantics easier to apply 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 states a specific verb and resource: 'Delete specific external breakpoints, or clear the whole external breakpoint set.' It clearly covers both modes of the tool and distinguishes it from related breakpoint tools by focusing on deletion rather than listing or setting.

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 examples provide clear usage scenarios: 'Clear all my breakpoints' maps to omitting ids, and 'Delete that breakpoint' maps to providing a structured id. It also explains when the no-ids path is preferable for a complete cleanup. It does not explicitly contrast with sap_set_breakpoint or sap_list_breakpoints as alternatives, but the intended usage is clear.

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