Simulates a single key press or key combination at the page level to trigger shortcuts, submit forms, or navigate. Accepts Playwright key strings like Enter and Control+A.
Send a single key or key combination at page level.
| Name | Required | Description | Default |
|---|---|---|---|
| key | Yes | Playwright key string, e.g. Enter, Control+A, ArrowDown. |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the entire behavioral burden. 'Single key or key combination' hints that held/repeated keypresses are not supported, but it says nothing about the focus requirement (does a focusable element need to be active?), whether events dispatch to the focused element or document, or any return value.
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. It is arguably over-terse for a tool whose behavior depends on focus state, but as pure structure it is clean and readable.
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 full schema coverage and no output schema, minimal text is defensible, but the description omits the interaction precondition (focus) that an agent needs to call this correctly in a page-level keyboard context.
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%, so the schema already documents the key parameter with Playwright key syntax examples. The description's 'single key or key combination' loosely maps to that but adds no new syntax or format 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?
States a specific verb (send) and resource (key/key combination) and scopes it to 'page level', which distinguishes it from element-targeted interaction tools like browser_type. It does not, however, name or contrast with any sibling explicitly.
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 prerequisites, and no alternative named. An agent must infer on its own that this is for keyboard shortcuts or key events versus browser_type for text entry into a field.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.