mcp-abap-adt

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool lists files and returns parsed JSON, but lacks details on permissions, rate limits, error handling, or whether it's read-only or mutative. This leaves significant gaps in understanding the tool's behavior.

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, efficient sentence that front-loads the key information ('List ABAP profiler trace files') and adds necessary detail ('Returns parsed JSON payload'). There is no wasted text, making it highly concise and well-structured.

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?

Given the tool's complexity (listing files) and lack of annotations or output schema, the description is minimally adequate. It covers the basic purpose and return format, but misses behavioral context (e.g., safety, limitations) and deeper usage guidance, leaving room for improvement.

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 tool has 0 parameters with 100% schema description coverage, so the schema fully documents the inputs. The description does not add parameter details, which is acceptable here, but it could have mentioned implicit constraints (e.g., no filtering options). Baseline is 4 due to zero parameters.

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 resource ('ABAP profiler trace files available in ADT runtime'), which is specific and informative. However, it does not explicitly differentiate from sibling tools like 'RuntimeListDumps' or 'RuntimeGetProfilerTraceData', which limits the score to 4 instead of 5.

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 on when to use this tool versus alternatives. The description mentions the tool's purpose but offers no context about prerequisites, timing, or comparison to related tools like 'RuntimeAnalyzeProfilerTrace' or 'RuntimeGetProfilerTraceData', leaving usage unclear.

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