browser_press

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the key-name format (Playwright, modifier syntax such as Control+a), which is useful, but says nothing about where the key is dispatched (focused element vs. page), whether it waits, or what happens if no element is focused.

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 that leads with the action and then supplies the format and examples. Nothing is wasted and no filler is present.

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 simple one-parameter tool with no output schema, the description is minimally adequate but leaves an important gap: it never says which element receives the key press or what state the browser must be in. With no annotations to compensate, that omission keeps it at 'minimum viable'.

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?

With one parameter at 100% schema coverage and no enums, the baseline is 3. The description goes beyond the schema's terse 'Key name' by naming the accepted convention (Playwright key names) and giving concrete examples like 'Control+a' and 'ArrowDown', which materially clarifies syntax.

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') and clarifies the input domain as Playwright key names. It is clearly distinguishable from siblings like browser_type and browser_click, though it never explicitly names or contrasts with those siblings.

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 explicit guidance on when to use this tool versus browser_type, browser_click, or browser_find. The key examples hint at the keyboard-interaction domain but do not state prerequisites such as requiring a focused element or a prior navigation.

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