Evaluate ABAP Debug Expression

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

Annotations already mark the tool read-only and idempotent; the description adds important behavioral context: variable IDs are resolved, not expressions, and scope determines visibility. It also documents the response shape. The only minor weakness is that 'Returns (json)' is not fully reconciled with the response_format parameter, but this does not undermine the behavioral disclosure.

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?

Front-loaded with the core action, followed by a high-value limitation note, compact arg summary, return shape, and targeted error handling. Every sentence earns its place; no fluff or duplication beyond the concise Args list.

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?

With no output schema, the description supplies the return shape, error behavior, and a route to the correct sibling. The dependency on a previous sap_debug_attach session is covered by the schema's session_id description. The slight return-format ambiguity is a minor issue against an otherwise complete definition.

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 parameter meaning is mostly carried by the schema. The description adds value by clarifying that expression means an ABAP variable ID rather than a computed expression and by giving concrete examples, slightly exceeding the schema's baseline.

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?

States a specific action ('Read one variable at the current stop point') and distinguishes itself from the sibling sap_debug_variables by noting it does not list all locals. It also clarifies that the tool resolves variable IDs, not computed expressions, despite the title's word 'Evaluate'.

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?

Gives clear when and when-not guidance: use for one specific variable at the current stop point; explicitly advises using sap_debug_variables when a variable is not in scope. Also warns against computed expressions because no evaluate-expression service exists.

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