sap_type

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

With no annotations, the description carries the full behavioral burden. It implies keys go to the currently selected window (a real risk if focus is wrong) but says nothing about whether existing field content is overwritten, permission/focus requirements, or how the operation reports success or failure.

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?

Two short, front-loaded sentences with zero filler; the primary purpose leads and the disambiguation follows immediately.

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?

No output schema and no annotations, yet the description omits focus prerequisites, overwrite behavior, and any explanation of the two screenshot parameters. For a 3-parameter interaction tool this leaves significant gaps an agent must guess at.

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 description coverage is 0% for 3 parameters, and the description only hints at the 'text' parameter semantics ('text/special keys'). The screenshot-related parameters (return_screenshot, as_file_target_folder) are undocumented in both schema and description, so no compensation occurs.

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 states a specific verb (Type) and mechanism (WScript SendKeys) targeting a defined resource (the selected SAP window), and explicitly contrasts itself with the sap_set_field sibling. An agent can distinguish this from sap_set_field and sap_press without opening any schema.

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?

It gives one explicit routing rule: use sap_set_field for literal text, implying this tool is for special/non-literal keys. It does not state prerequisites (window must be focused/selected) or when NOT to use it, but the alternative is named concretely.

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