List ABAP Traces

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only the service mechanism ('ADT trace services') but no additional behavioral details like pagination limits or response structure. 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, front-loaded sentence with no wasted words. It is concise, but it adds only the phrase 'through SAP ADT trace services' beyond the title, which is slightly redundant. Still, it earns a high score for brevity.

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?

The presence of an output schema and annotations reduces the need for the description to explain return values or safety. However, the description is minimal and does not provide context on how listing works, pagination, or when to adjust parameters like limit and startIndex. It is adequate for a simple list tool but lacks richer contextual guidance.

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?

The description provides no information about any of the four parameters. Schema description coverage is 0%, so the description fails to compensate for the schema's lack of semantic context. The parameter names are self-explanatory to some degree, but the description adds zero value beyond the schema.

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 ('List') and the resource ('ABAP Traces'), and specifies the mechanism ('through SAP ADT trace services'). This distinguishes it from sibling trace tools like inspect, hit_list, or configuration.

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 provided about when to use this tool versus alternatives. It does not mention scenarios for listing traces, nor does it exclude cases better suited to other trace-related tools such as sap.runtime.trace.inspect or sap.runtime.trace.hit_list.

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