mcp-abap-adt

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

No annotations are provided, so the description carries full burden. It discloses the return format ('parsed JSON payload') and mentions filtering/paging behavior, but doesn't cover rate limits, authentication needs, error conditions, or whether this is a read-only operation (though 'List' implies it likely is).

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?

Single sentence with zero waste - every word contributes essential information: resource, optional filters, paging, and return format. Perfectly front-loaded with the core purpose.

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 read operation with no annotations and no output schema, the description adequately covers the basic purpose and return format. However, it lacks details about response structure, error handling, or system-specific constraints that would be helpful given the tool's complexity and lack of structured metadata.

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 100%, so the schema fully documents all 5 parameters. The description adds marginal value by mentioning 'optional user filter and paging' which aligns with the schema, but doesn't provide additional syntax or format details beyond what the schema already specifies.

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 verb ('List'), resource ('ABAP runtime dumps'), and scope ('with optional user filter and paging'). It distinguishes from siblings like RuntimeGetDumpById (which gets a specific dump) and RuntimeAnalyzeDump (which analyzes a dump).

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?

The description implies usage for listing dumps with filtering/paging, but doesn't explicitly state when to use this vs. alternatives like RuntimeGetDumpById or RuntimeListProfilerTraceFiles. No prerequisites or exclusions are mentioned.

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