Evaluate ABAP Debug Expression

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering the safety profile. The description adds the requirement of an 'attached debug stack frame,' which is a useful behavioral precondition, but it does not disclose what happens when no frame is attached or how the expression is evaluated (e.g., side effects on debugger state). With annotations carrying the safety burden, this is adequate but not rich.

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 with no filler, front-loading the core action and resource. It is appropriately concise for a tool with a clear purpose, though the brevity contributes to the lack of parameter guidance.

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?

Despite the presence of an output schema and annotations, the tool has 11 parameters with zero description coverage and no usage context. The description does not explain how to obtain the required frameId, what an 'attached debug stack frame' means, or how this tool fits within the larger debug workflow (e.g., after sap.debug.stack). This is insufficient for a tool of this complexity.

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 compensate, but it only implicitly references the 'expression' parameter. The other 10 parameters (systemId, frameId, filter, rowCount, etc.) are completely unexplained, leaving the agent without semantic meaning for required inputs beyond their bare schema types.

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 action ('Evaluate one expression') and the resource ('attached debug stack frame'), distinguishing it from sibling debug tools like sap.debug.variables (which lists variables) and sap.debug.stack (which shows stack frames). The verb and scope are specific and unambiguous.

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, nor any prerequisites or exclusions. It does not mention that a debug session must be active or how to obtain a valid frameId, leaving the selection decision to the agent without context.

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