Execute ABAP Application

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

Annotations indicate destructiveHint=true, but the description does not detail potential side effects or what executing a plan entails (e.g., modification of system state, data changes). The confirmation parameter hints at a safety mechanism, but no explanation is given.

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 concise sentence, but it is too sparse. It achieves conciseness at the cost of completeness, missing important contextual details.

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?

With 3 required parameters, no schema descriptions, destructive behavior, and an output schema (not detailed), the description is grossly insufficient. An agent cannot determine how to properly invoke the tool, interpret the confirmation string, or anticipate outcomes.

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 0%, and the description adds no detail about the parameters. planId is vaguely tied to 'plan', confirmation is mentioned but not defined, systemId is entirely unexplained. The description fails to add meaning beyond field names.

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 identifies the action ('Execute') and the resource ('confirmed ABAP application plan'). It distinguishes from siblings like sap.execution.preview (preview vs. execute) and sap.execution.health (monitoring). However, it does not clarify what 'confirmed' means or how the confirmation parameter relates.

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 explicit guidance on when to use this tool vs. alternatives (e.g., sap.execution.preview). No prerequisites or context provided. The agent must infer that a plan must exist and be confirmed, but this is not stated.

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