desktop_key

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

With no annotations, the description must carry the full burden, and it does disclose the key behavioral trait: input goes to whatever window currently has focus, so results depend on desktop state. It says nothing about side effects (keystrokes go to a live desktop), failure modes (no focused window), or what `verify`/`verifyRegion` do.

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 sentences, front-loaded with the action and examples, then the targeting constraint. Every sentence carries information; no padding.

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 three-parameter input tool with no annotations and no output schema, the description covers what it does and where input lands, which is the minimum an agent needs. It leaves the verification parameters and return/error semantics unexplained, which is a real gap given `verify` is entirely undocumented.

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 67%, and the description merely repeats the combo examples already present in the schema's `combo` description. The `verify` boolean has no description anywhere, and the description does not compensate for that undocumented parameter or explain what verifyRegion comparison returns.

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?

States a specific action (send a key combo) with concrete examples (ctrl+c, alt+tab, f5) and the target scope (current focused window). This separates it in practice from desktop_type, though the sibling is never named, so differentiation is inferred rather than explicit.

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 note that it acts on the currently focused window implicitly tells the agent it must focus a target window first (e.g. via desktop_focus_window), which is useful implied guidance. There is no explicit when-to-use vs desktop_type or desktop_click_element, and no when-not-to-use.

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