browser_press_key

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

No annotations provided, so description carries full burden. The description is too brief: it does not disclose prerequisites (e.g., requiring a focused element), side effects, or behavior beyond the basic action.

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?

Very short (one sentence) but references browser_docs, which adds some utility. However, it could be more structured and informative without being verbose.

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 low complexity, the description is insufficient: it does not explain modifiers (e.g., 'Control+A'), target context, or if the key press is sent globally or to an element.

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% with one parameter having a clear description. The description adds no new meaning beyond the schema's 'The key to press'. Baseline 3 is appropriate.

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 sends a keyboard event (press a key) and distinguishes from similar tools like browser_click (mouse) and browser_type (typing text). The verb 'send a keyboard event' is specific and the resource is a key press.

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 implies usage for single key presses but does not explicitly compare with alternatives like browser_type for sequences. It references browser_docs for more details but lacks direct guidance on when to use or when not.

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