Press a key

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

The description adds some context by explaining the key types and the ability to target an element, but does not disclose potential side effects like form submission or focus changes beyond the annotation hints. The annotations indicate non-read-only and non-destructive, which the description does not contradict, but it provides only marginal transparency.

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?

The description is two sentences, immediately states the action, and provides relevant key examples without irrelevant information. It is appropriately sized and front-loaded.

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?

Given the complex schema with nested target object and annotations, the description is sufficient to convey the core action, but it lacks details on return values, error handling, and edge cases like invalid keys or missing targets. The schema covers parameter semantics but not behavioral outcomes.

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?

The description supplements the schema with additional Playwright key examples (ArrowDown, PageDown, Backspace) and notes that keys can be sent to the page or focused element, which aligns with the target parameter. However, the schema already covers key details and target descriptions, so the added value is limited.

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 clearly states 'Send a keyboard key to the page or to a focused element', identifying the specific verb and resource. It also lists Playwright key names, which distinguishes it from sibling tools like browser_type (typing text) and browser_click (mouse click).

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?

The description implies usage for keyboard actions but does not explicitly state when to use this tool over alternatives like browser_type or browser_click. There is no when/when-not guidance, only the action description itself.

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