Press key

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 does not disclose that Enter submits forms by default (only inferable from the noSubmit param), nor what trusted, delay, waitUntil, or timeout do, nor what happens on failure.

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?

Two compact sentences, front-loaded with the concrete key examples, with no filler. Efficient, though the second sentence is thin relative to the tool's complexity.

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?

A 10-parameter browser automation tool with no annotations and no output schema needs substantially more description than two sentences. Key behaviors (form submission, trusted input, wait semantics, failure modes) are all missing.

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 only 10% (just noSubmit), so 9 of 10 parameters are undocumented. The description adds useful key-syntax examples and mentions focusing an element, but leaves delay, tabId, frameId, timeout, trusted, waitUntil, and selector semantics entirely unexplained.

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?

States a specific verb (press) and resource (key or key combination), and the examples (Control+A, Shift+Enter, F5) make clear this is for keystrokes rather than typing text. It does not explicitly contrast itself with the sibling 'type' tool, so an agent must infer the boundary.

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?

'Optionally focus an element first' hints at the ref/selector parameters, but there is no guidance on when to use press versus type or click, nor any stated prerequisites or page-state conditions. Usage is left almost entirely to inference.

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