sap_execute_command

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

No annotations are provided, so the description carries the full burden. It clearly states that the tool submits arbitrary commands as if typed in the command field, but it does not disclose potential side effects, session requirements, or the fact that commands may navigate, mutate state, or log out. For an 'arbitrary command' tool, more cautionary transparency would be valuable.

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 focused sentence that front-loads the action and object. Every part contributes meaning, and there is no redundant filler or repetition of schema details.

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?

The tool is simple with one well-described parameter and an output schema is absent. However, the description omits guidance about side effects, when to use sap_execute_command versus sap_navigate, and what happens if no session exists. Given the tool's arbitrary-command nature, this leaves meaningful gaps.

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?

The schema already provides 100% coverage for the single 'command' parameter with a clear description and examples ('/nSE11', '=back', '/nEXIT'). The tool description does not add extra parameter semantics beyond the schema, so the baseline score of 3 is 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?

The description clearly identifies the verb ('Submit'), the resource ('arbitrary command string'), and the target context ('current SAP WebGUI session'). The phrase 'as if typed in the command field' precisely conveys the tool's scope and distinguishes it from sibling tools like sap_navigate or sap_run_report.

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 implies when to use the tool—whenever an arbitrary OK code or transaction command needs to be submitted to the current session. However, it does not explicitly state when to prefer this over alternatives like sap_navigate, nor does it mention prerequisites or exclusions.

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