AmdpDebugSetBreakpoints

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

With no annotations provided, the description carries the full burden, and it does disclose meaningful behavior: the set is applied server-side ('as confirmed by the system'), it catches requests for the whole connected SAP user from any source (a broad, surprising side effect), and it does not work in batch mode. However, it does not state that existing breakpoints are replaced, what permissions are required, or what happens when the session has ended.

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?

Three short sentences with the tag prefixes front-loaded and no filler. The clause 'as confirmed by the system' is slightly vague, but overall the text is tight and appropriately sized for a three-parameter tool.

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?

Honestly this is a 3-ish area, but weighing it: no output schema exists, so the description would ideally say what comes back; the 'detail' enum in the schema covers return granularity, which mitigates that gap. For a stateful debug mutation the description gives the environment constraint (no batch mode) and the scope of effect (all requests of the user), which is the core operational context an agent needs before calling.

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 state_handle, breakpoints, and detail are already fully documented in the schema, giving a baseline of 3. The phrase 'to the set given' hints that the breakpoints array replaces rather than appends, which is a small semantic addition, but no other parameter meaning is added.

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: 'Sets the AMDP breakpoints of a debug session to the set given.' The AMDP qualifier and the note about catching requests 'from this server and from anywhere else' implicitly separate it from the generic DebugSetBreakpoints sibling, but the sibling is never named, so an agent must infer which tool to pick.

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?

There is no explicit statement of when to use this versus DebugSetBreakpoints, nor any prerequisite such as needing an active session created by AmdpDebugStart. The only exclusion hint is the trailing 'Runs outside batch mode,' which is a constraint, not usage guidance.

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