browser_press_key

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

With no annotations provided, the description carries the full burden, but it only states the action itself. It does not disclose focus requirements, whether key combinations/modifiers are supported, whether the page might navigate or change, or what the function returns after pressing the key.

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?

A single, direct, front-loaded sentence with no filler or redundant wording. It conveys the core action immediately and is appropriately sized for a simple tool.

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 definition is complete enough only at a surface level. It lacks important context such as prerequisites (focused element, loaded page), support for modifier keys, potential side effects, and any return/acknowledgment behavior. Since there is no output schema, this behavioral gap is more significant.

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 100%, so the schema already documents all parameters well. The description adds no new meaning beyond 'specified tab,' which merely references the tabId parameter. This meets the baseline for fully documented schema parameters.

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?

Describes a specific action ('Press a keyboard key') with a clear target resource (keyboard key) and scope (specified tab). This clearly distinguishes it from sibling tools like browser_click (mouse action), browser_type (text input), and browser_navigate (page navigation).

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 guidance is given on when to use this tool versus alternatives such as browser_type or browser_evaluate. It does not mention when not to use it, nor does it explain whether it is intended for shortcuts, special keys, or text entry.

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