browser_press_key

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that — it doesn't warn that a key press can submit forms, trigger navigation, or fire dialogs, which is exactly the extra context this destructive tool needs.

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?

It is a single front-loaded sentence with no waste, but its brevity reflects under-specification rather than disciplined concision — there is room for a short clause on modifiers or focus prerequisites.

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 destructive, open-world browser action with no output schema, the definition is too thin: it says nothing about what state the page must be in, what side effects may follow, or how it relates to the other ~28 browser tools.

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% and both parameters (key, session) are documented in the schema, including the example formats `ArrowLeft` and `a`. The description contributes no additional meaning, but baseline 3 applies when the schema carries the burden.

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'), but it is essentially a restatement of the tool name and adds no distinguishing scope. With siblings like browser_type, browser_fill_form, and browser_click, an agent cannot tell from this sentence what makes key-press distinct (e.g., support for modifier chords or special keys).

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 when-to-use guidance, no mention of alternatives such as browser_type for entering text, and no note about requiring a prior focus/snapshot action. The agent must infer everything about sequencing from context.

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