browser_press_key

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

With no annotations provided, the description must fully disclose behavior. It only mentions that the action returns a snapshot, but fails to describe side effects, focus requirements, whether keys are released, or if there are any timing considerations.

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?

Single sentence with examples, front-loaded, no redundant words. Efficient and to the point.

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 the tool's simplicity and the presence of an output schema, the description covers the basic functionality. However, it lacks context on valid keys (only examples), session management, and interaction with other browser elements. Sibling tools are numerous, so more guidance would help agent selection.

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 description coverage is 0%, so the description must compensate. It gives examples for the 'key' parameter but does not explain the 'session_id' parameter or its optional use. Missing details like allowed key values (beyond examples) or format.

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?

The description clearly states the action ('Press a keyboard key'), specifies the resource ('keyboard key'), and provides concrete examples ('Enter', 'Escape', 'ArrowDown', 'Tab'). It distinguishes from sibling tools like browser_click or browser_keyboard_type.

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?

No guidelines on when to use this tool versus alternatives like browser_keyboard_type or browser_fill_form. No mention of prerequisites (e.g., focus on an input element) or when not to use it.

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