GetRuntimeDumps

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

With no annotations, the description provides minimal behavioral information. It does not disclose side effects (likely a read-only operation), result ordering, error handling, or authentication requirements. The parameter descriptions give some format constraints but not behavior beyond retrieval.

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, concise and front-loaded with the core action. However, it is too sparse, omitting important context. It earns its place but does not fully inform the agent.

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 6 parameters, no output schema, and no annotations, the description is inadequate. It does not explain the purpose of runtime dumps, how results are formatted, or how to handle edge cases like no results. The agent lacks sufficient context for correct tool invocation.

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 coverage is 100% with parameter descriptions explaining formats and defaults. However, the tool description adds no extra meaning beyond the schema. For example, 'Category filter' is not explained. The baseline of 3 is appropriate as the schema does the heavy lifting.

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 'Retrieve' and the resource 'ABAP runtime dump list', indicating it returns a list of dumps. It distinguishes from the sibling tool 'GetRuntimeDumpDetails' which likely retrieves a single dump's details. However, it could be more explicit about the list nature and what constitutes a runtime 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?

There is no guidance on when to use this tool versus alternatives like 'GetRuntimeDumpDetails'. It does not state prerequisites, typical use cases, or scenarios to avoid. The agent must infer usage from the tool name and siblings.

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