sap_send_key

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

Annotations only provide readOnlyHint=false and destructiveHint=false. Description adds a critical behavioral detail: 'F11 / Save requires user confirmation via elicitation before proceeding.' This discloses a prerequisite for a specific key that could affect automation.

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?

Three sentences, front-loaded with the action and common keys. Each sentence adds value: action + common keys + special behavior for F11. No wasted words.

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 parameter and output schema exists (so return values are covered). The description explains the parameter well and highlights a behavioral trap (F11 confirmation). Could mention error handling for invalid keys, but enum prevents 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 coverage is 0% but the parameter is an enum of 30 keys. The description maps common enum values to their SAP functions (e.g., F1=Help, F11=Save with confirmation note). This adds meaning beyond the enum names alone.

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?

Clearly states the verb 'Press' and the resource 'keyboard key / function key in the SAP window'. The list of common keys further clarifies the purpose and distinguishes it from sibling tools like sap_press_button.

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?

Provides a list of common keys with their functions (e.g., Enter confirm, F1 Help) but does not explicitly state when to use this tool versus alternatives like pressing a button. Usage context is implied rather than directed.

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