browser_press_key

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

With destructiveHint=true and readOnlyHint=false, the annotations already indicate this action can mutate state. The description adds no behavioral context beyond the hint, such as possible effects like triggering shortcuts, navigation, or needing an active element.

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 clear sentence with no filler, repetition, or unnecessary detail. It is appropriately sized for such 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?

For a one-parameter tool with complete schema documentation and safety annotations, the description is minimally viable. However, it does not explain when to use this tool, what happens after pressing a key, or how it relates to siblings like browser_type.

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 covers the only parameter (key) with a clear description and examples like ArrowLeft or a. Since schema coverage is 100%, the description does not need to add parameter meaning, and it does not provide extra detail 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 states a specific verb and resource: 'Press a key on the keyboard.' It clearly identifies the tool's function, though it does not explicitly differentiate it from siblings like browser_type or browser_click.

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 provides no guidance on when to use this tool versus alternatives. It does not mention cases where browser_type would be more appropriate, nor does it describe context such as focus requirements or typical use.

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