Call BAPI with Commit/Rollback

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

Annotations already mark destructiveHint=true and readOnlyHint=false, and the description adds autocommit/rollback behavior, ABAP error-type handling, and a warning about creating/changing/deleting business objects. No contradiction exists; the description significantly enriches the annotation profile.

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 well-structured with the warning first, followed by args, return format, and an example. Each section contributes, though the Args section partially duplicates schema parameter descriptions. Overall it is efficient and front-loaded.

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 complex mutation tool with no output schema, the description explains the return JSON structure including the committed flag, RETURN table entries, and transaction outcomes. It is sufficiently complete for an agent to invoke the tool correctly and understand side effects.

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 the baseline is 3. The description adds the constraint that bapi_name must be RFC-enabled and provides a concrete example mapping 'Create a purchase order' to BAPI_PO_CREATE1, which adds practical guidance beyond the schema.

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 specifies the verb 'Call' and resource 'BAPI function module', and clearly highlights commit/rollback semantics. It does not explicitly distinguish from sibling sap_rfc_call, but the BAPI-specific transaction handling makes the purpose unambiguous.

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 includes a warning to use only in development/sandbox unless certain of the effect, which is useful context. However, it does not state when to choose this tool over alternatives like sap_rfc_call or sap_read_table, nor does it provide any when-not conditions.

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