keyboard_key

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

No annotations are provided, so the description carries the behavioral disclosure burden. It explains accepted formats and gives examples, but does not mention whether the press targets the active window, whether it blocks, or what happens on invalid keys. This is adequate but not detailed.

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 front-loaded with the core action and immediately provides high-value examples. The 'Parameters' section is somewhat redundant with the schema, but it adds concrete format examples and does not include unnecessary prose.

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 single-parameter keyboard tool with an output schema, the description provides enough to invoke correctly: what it does, valid input formats, and examples. It omits whether the target is the foreground window, but that is an implied prerequisite in the context of sibling focus_window and other desktop automation tools.

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 only defines keys as a string, but the description adds meaningful detail by showing accepted formats ('enter', 'ctrl+c', 'alt+tab') and labeling them 'human-friendly combos.' This compensates for the 0% schema description coverage.

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?

Opens with a specific verb and resource: 'Press a key or key combination.' The examples ('ctrl+c', 'alt+f4') clearly distinguish it from sibling keyboard_type, which would type strings rather than execute key combinations.

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 phrase 'Accepts human-friendly combos' and the examples imply usage for keyboard shortcuts, but there is no explicit guidance on when to prefer this over keyboard_type or whether a window must be focused first. No alternatives are named.

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