RuntimeGetDumpById

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

The description indicates this is a read operation ('Read'), which is transparent. Without annotations, the description carries the burden, and it adequately discloses that the tool fetches existing dump content without side effects. It adds context beyond schema by linking to RuntimeListFeeds.

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 extremely concise with two short sentences. It front-loads the purpose and immediately provides a workflow hint. No unnecessary words.

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 no output schema, the description doesn't detail the returned dump structure, but the response_mode parameter describes possible outputs. The workflow hint integrates with sibling tool RuntimeListFeeds. Completeness is adequate for a read operation.

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%, so baseline is 3. The description adds minimal extra meaning beyond what the schema already provides (the schema already mentions 'e.g. from RuntimeListFeeds' for dump_id). The description reinforces the workflow but doesn't elaborate on view or response_mode beyond their schema definitions.

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 'Read a specific ABAP runtime dump by its ID', which is a specific verb-resource pairing. It also distinguishes from sibling tools by mentioning the prerequisite step of using RuntimeListFeeds, showing how this tool fits in a workflow.

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 provides explicit guidance: 'First use RuntimeListFeeds to find dumps and get their IDs, then pass dump_id here'. This tells when to use the tool and the required preceding step, though it doesn't explicitly mention when not to use it.

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