Press Key

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

Description accurately describes pressing a key, listing many specific keys. No annotations exist, so description carries full burden. Provides good detail without contradiction.

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: first states purpose, second lists accepted formats. No wasted words. Could be slightly shorter but effective.

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?

Given simplicity (2 required params, no output schema) and informative sibling context, description covers essentials. No need for additional details like return value or error cases.

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 100% so baseline is 3. Description adds example values for 'key' parameter but no new semantics beyond what schema description provides.

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 clearly states it presses a hardware/system key. Lists many friendly names and raw keycode option. Distinct from sibling tools like tap, double_tap, long_press which are touch-based, and type_text which inputs text characters.

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?

Description explains accepted key formats (friendly names or raw keycode). Does not explicitly say when to use vs alternatives, but given sibling names, context is clear.

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