sap_execute_transaction

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

Discloses that it navigates to initial screen, subject to blocklist/allowlist, and includes /n prefix requirement. Annotations indicate non-read-only and non-destructive, consistent with description. No contradiction.

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?

Concise three-paragraph structure: core action, usage guidance, and constraints. Every sentence adds value, front-loaded with key information.

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?

Covers all important aspects: execution, screen navigation, special prefixes, restrictions, and cross-reference to related tool. Output schema exists, so return values are already documented.

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?

Only parameter 'tcode' is documented with examples and prefix guidance, compensating for 0% schema description coverage. Provides practical usage details beyond 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 clearly states the tool executes SAP transaction codes, provides examples (MM03, VA01, SM30), and distinguishes from sibling tools like sap_get_transaction_guide by focusing on starting the 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?

Explicit guidance on checking screen info from response, /n prefix for SCWM, blocklist/allowlist, and recommending sap_get_session_info before navigating away. Clearly tells when to use and what to check.

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