sap_send_vkey

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

No annotations are provided, so the description carries the full disclosure burden. It never states what happens on failure (e.g. no session configured), what the response contains, or whether the call mutates UI state, which it clearly does. The only behavioral hint is the parenthetical that 0 maps to Enter.

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?

One tight sentence with no wasted words, and the key-mapping detail is placed inline where it is most useful. It is short to the point of under-specification rather than bloated, so it earns most of its space.

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 mutation-style input tool with no annotations and no output schema, the description omits critical context: how the target session is established, what a successful or failed send looks like, and how to find the key-code table it references. An agent cannot reliably call this without that information.

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% and the single integer parameter (0-134) is undocumented in the schema, so the description must compensate. It partially does by saying it is a documented SAP virtual key and giving one concrete mapping (0 = Enter), but 133 other codes and the notion of 'documented' are left unexplained.

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 gives a specific verb and resource: sending a virtual key code to the configured SAP session. That is enough to understand what it does, but it does not differentiate itself from the sibling sap_press, which plausibly also sends keystrokes, leaving the agent to guess which key-sending tool applies.

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?

There is no guidance on when to use this versus sap_press, sap_type, or sap_click, and no stated prerequisite such as an active session being required. The only implicit context is 'configured session', which the agent must infer.

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