Execute ABAP Version Restore

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description adds little behavioral context. 'Fresh version-restore plan' implies a new restore, but no details on side effects, reversibility, or system impact beyond what annotations provide.

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, which is concise but at the expense of completeness. It omits critical information about parameters and usage context, making it insufficiently informative.

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 destructive tool with three required parameters and no parameter descriptions, the description lacks context about how to obtain a plan, what confirmation value to use, and the overall workflow. Its brevity fails to compensate for missing schema details.

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 0% (no parameter descriptions in schema). The description does not explain the three required parameters (planId, systemId, confirmation), their meaning, format, or constraints, leaving the agent without essential guidance.

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?

Description states verb 'Execute' and resource 'version-restore plan' with qualifiers 'confirmed' and 'fresh'. It is specific but does not differentiate from sibling execute tools like sap.execution.execute or sap.refactor.execute, which also perform actions.

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 on when to use this tool versus alternatives, nor prerequisites such as needing a confirmed plan from a preview tool. The description does not explain what 'confirmed fresh' means or how to obtain such a plan.

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