browser_press_key

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

Annotations already flag destructiveHint=true and readOnly=false, so the agent knows this action can mutate state. The description adds no additional behavioral context such as side effects, focus requirements, or whether a page must be loaded. No contradiction, but little transparency beyond the plain 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?

The description is a single short sentence that is easy to parse and front-loaded with the action. Slight redundancy exists in 'on the keyboard,' but it remains appropriately concise.

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 one-parameter tool with a fully documented schema and safety-relevant annotations, the description is minimally adequate. It lacks useful context about keyboard focus and how this differs from browser_type, but the low complexity means the missing detail is not severe.

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 schema fully documents the single key parameter with a description and examples ('ArrowLeft' or 'a') at 100% coverage. The description adds no parameter details beyond what the schema already provides, so the baseline of 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 states a specific verb ('Press') and resource ('a key on the keyboard'), making the core intent immediately clear. It does not explicitly distinguish itself from the sibling browser_type, which is also keyboard-related, so it is not fully differentiated.

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?

There is no guidance on when to use this tool versus browser_type, browser_click, or browser_fill_form, and no mention of prerequisites such as requiring focus on an element. The intended usage context is left entirely to inference.

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