press_key

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

Description states it presses a key, which implies a write action; annotations show readOnlyHint=false, consistent. However, no details on side effects (e.g., focus requirements, invalid key handling) beyond the action itself.

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 covering action, usage context, and examples. No fluff, front-loaded with the verb and resource.

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 simple tool with full schema and no output schema, the description adequately covers purpose and usage. Could mention that it operates on the currently focused element, but not strictly necessary.

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?

All parameters (key and includeSnapshot) are fully described in the schema. Schema coverage is 100%, so description adds no extra parameter meaning beyond what schema already 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?

Clearly states the tool presses a key or key combination, with examples like 'Enter' and 'Control+A'. Distinguishes from filling by specifying it's for shortcuts/navigation when fill() cannot be used.

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?

Explicitly says 'Use this when other input methods like fill() cannot be used' and lists typical scenarios (keyboard shortcuts, navigation keys, special combinations). This provides clear when-to-use guidance and implies alternatives.

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