browser_press_key

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

With no annotations, the description carries the full burden, but it only restates the action ('Press a key') and adds iframe targeting. It does not disclose behavior like event sequencing, modifiers, focus requirements, or potential side effects such as navigation. This is a minimal disclosure with little added context.

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 two short sentences, precisely front-loaded with the action ('Press a key') and examples. Every word earns its place without unnecessary detail.

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?

The tool is simple with two documented parameters and no output schema. The description covers the main action and the iframe nuance, but lacks any note about edge cases, wait behavior, or what happens if the key press triggers navigation, making it adequate but not rich.

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 input schema already describes both parameters (key, frameSelector) with examples, so schema coverage is 100%. The description adds a note about using frameSelector to send to an iframe, which is slightly clearer than the schema's 'target the frame', but does not add significant meaning 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?

The description clearly states the tool presses a key and gives examples (Enter, Tab, ArrowRight). It distinguishes from sibling tools like browser_click and browser_type by focusing on key presses, though it does not explicitly compare. The verb 'Press' is specific and the resource is 'key'.

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 description gives context that keys like Enter/Tab/ArrowRight can be pressed and mentions using frameSelector for iframes, but it does not explicitly state when to prefer this over browser_type or browser_click. It implies usage for key events, but no exclusions or alternatives are named.

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