rollback_rfc_transaction

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

Annotations already declare destructiveHint=true, idempotentHint=false, readOnlyHint=false, so safety is covered. The description adds real value beyond them: the policy-mode gate and the fact that it acts on state created by earlier call_rfc_function writes, which an agent could not infer from the annotations alone.

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?

Two tightly written sentences with the effect front-loaded and the availability constraint second; no filler and nothing repeated from structured fields.

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 single-required-param destructive tool with an output schema, the description covers the effect, the precondition, and the linkage to prior writes. Return values are covered by the output schema, so nothing needed for correct invocation is missing.

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% and the single transaction_id parameter is already documented as an opaque ID returned by the write call. The description adds only that the ID identifies a SAP transaction, so the schema does the heavy lifting and the baseline of 3 applies.

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?

Specific verb+resource: it discards changes staged by prior write call_rfc_function calls and names the underlying BAPI_TRANSACTION_ROLLBACK. An agent can immediately distinguish it from commit_rfc_transaction without opening either schema.

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?

States the precondition 'Only available when the server policy mode is read_write' and scopes the tool to changes staged by prior write calls, which implicitly routes the agent away from commit_rfc_transaction. It never names the alternative sibling or the inverse-condition explicitly, so it stops short of a 5.

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