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, and the description adds nothing on top of them – no indication that a keypress acts on whatever is currently focused, that it can trigger destructive page actions, or how the session target interacts with behavior. The description carries zero behavioral value and contradicts nothing, so it sits at the bottom rather than a contradiction.

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 front-loaded sentence with no wasted words, which is structurally clean. But the terseness reads as under-specification rather than genuine conciseness – nothing beyond the minimum verb+resource is included.

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 browser-input tool flagged destructive and open-world, with no output schema and no guidance in the description, an agent lacks the context to call it safely (focus requirements, session behavior, what a keypress may trigger). The structured fields alone do not cover this gap.

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%: the schema explains both the `key` parameter (e.g. `ArrowLeft` or `a`) and `sessionId` (omit to use active session). The description adds no syntax or naming detail beyond the schema, so the baseline 3 applies.

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 gives a concrete verb+resource ('Press a key on the keyboard'), so the basic action is unambiguous. However, it offers no differentiation from close siblings like browser_type or browser_fill_form, which also send keyboard input, leaving an agent to infer the boundary. Vague-but-adequate: purpose is stated, the distinction from siblings is not.

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 statement of when to use this tool versus browser_type (typing text) or browser_fill_form, and no preconditions such as the need for an element to be focused first. Usage must be entirely inferred from the name. This is the 'no guidance' tier.

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