Read ABAP Trace Statements

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint: false, so the safe read-only nature is covered. The description adds only 'through SAP ADT trace services' as extra behavioral context, which is minimal. No contradiction with annotations.

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 fluff or redundancy. It is concise and front-loaded, but arguably too terse to serve as functional 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 accurate annotations and an output schema, the description lacks critical usage context. It doesn't differentiate from sibling trace tools, doesn't explain when to use it, and gives no parameter semantics. The tool's complexity demands more than one sentence.

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 description coverage is 0% and the description adds no explanations for the 5 parameters (systemId, traceId, limit, startIndex, includeDetails). The only implicit hint is that a trace is involved, but this is far from sufficient.

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 a read operation on ABAP Trace Statements via SAP ADT trace services, using a specific verb and resource. It does not explicitly distinguish from sibling trace tools like sap.runtime.trace.hit_list or sap.runtime.trace.inspect, but 'statements' is a distinct resource.

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?

No guidance is given on when to use this tool versus alternatives such as sap.runtime.trace.list or sap.runtime.trace.inspect. The description neither mentions prerequisites (e.g., needing a traceId) nor exclusions/alternatives.

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