commit_rfc_transaction

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

Annotations already declare destructive, non-idempotent, and open-world behavior, so the bar is lower, and the description still adds real value: the underlying BAPI, that it persists (rather than reads) staged state, and the read_write policy precondition. It stops short of describing post-commit transaction state or error semantics, which the output schema may partly cover.

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 tight sentences with the core action front-loaded and the operational precondition appended. No redundant restatement of the tool name or schema.

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 a 2-parameter schema at full coverage, rich annotations, and an output schema, the description covers the essential workflow and availability constraint. The main minor gap is that it doesn't discuss rollback behavior or failure handling, but the structured fields carry most of that.

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 100%, so transaction_id and wait are already fully documented in the schema. The description adds no format detail or usage nuance for either parameter, making the baseline 3 appropriate.

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?

States a specific verb (persist/commit) and resource (staged changes in the identified SAP transaction), and grounds it in the wrapping BAPI_TRANSACTION_COMMIT. It also references call_rfc_function as the operation whose changes it commits, distinguishing it clearly from rollback_rfc_transaction.

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?

Explains the workflow context ('changes staged by prior write call_rfc_function calls') and adds an explicit availability constraint ('only available when server policy mode is read_write'). It does not explicitly route the agent to rollback_rfc_transaction for the failure case, so an alternative-selection sentence is missing.

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