ABAP Debug Breakpoint

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description 'set or remove' aligns with this but adds no further behavioral context, such as whether breakpoints persist or require a session, which would enhance transparency.

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 a single sentence, concise and front-loaded. However, it could be more informative without losing brevity by including parameter hints or usage context.

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?

Given the tool's complexity (5 parameters, 3 required) and lack of output schema, the description is too sparse. It doesn't explain key aspects like the URI format, condition usage, or how breakpoints interact with other debug tools.

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?

With 0% schema description coverage, the description must clarify parameters, but it only mentions 'adt:// ABAP source URI', implicitly referencing filePath. The roles of connectionId, lineNumbers, condition, and action enum are left unspecified, forcing inference.

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 'Set or remove line breakpoints for an adt:// ABAP source URI' uses a specific verb ('Set or remove') and resource ('line breakpoints'), clearly distinguishing the tool from sibling debug-related tools like abap_debug_session or abap_debug_step.

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 alternative debug tools, nor does it mention prerequisites like an active debug session. No exclusions or alternatives are given.

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