RuntimeListProfilerTraceFiles

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

The description implies a read-only list operation but does not explicitly state non-destructiveness, permissions, or side effects. Since annotations are absent, the description partially bears the burden but still lacks explicit behavioral commitments.

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?

Two concise sentences front-load the purpose and output format. Every word adds value, and the structure is optimal for quick comprehension.

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?

For a zero-parameter list tool, the description fully covers what it does (list files), scope (ADT runtime), and output (parsed JSON). No additional context is needed given the simplicity.

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 input schema has zero parameters and 100% coverage. Per guidelines, zero params gives a baseline of 4. The description adds no parameter-specific info, but none is needed.

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 tool lists ABAP profiler trace files in ADT runtime, which is a specific verb and resource. It distinguishes from sibling runtime tools like RuntimeAnalyzeProfilerTrace or RuntimeGetProfilerTraceData that perform different actions.

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 on when to use this tool vs. alternatives. It does not mention prerequisites, typical workflow steps (e.g., list before getting data or analyzing), or scenarios where this tool is preferred.

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