press_key

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

Description discloses key-press behavior and syntax support, but does not mention side effects (e.g., if app requires focus, if keystrokes trigger actions). Annotations provide no behavioral hints, so description carries burden; moderate transparency.

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 sentences plus bullet examples, no redundant words. Front-loaded with core action. Efficient and scannable.

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; description omits outcome (e.g., return value, whether key press is guaranteed). Does not clarify if the app must be running/focused. Lacks guidance on systematic vs app-specific behavior.

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 covers both parameters with clear descriptions; description adds valuable examples and syntax details for the 'key' parameter, enhancing understanding beyond the schema.

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?

Description explicitly states 'Press a key or key-combination on the keyboard' with clear verb and resource. Includes modifier and navigation keys, distinguishing it from siblings like type_text or click.

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 examples and references xdotool syntax, but lacks explicit guidance on when to use this tool vs alternatives (e.g., type_text for text input, click for mouse). No when-not-to-use or prerequisite conditions.

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