press

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

The destructiveHint annotation is present, but the description adds no behavioral detail beyond 'press a key' — it does not say what side effects can occur (e.g., navigation, shortcut triggering, form submission) or what exactly is destroyed. With the annotation carrying the only risk signal, the description contributes little 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 short and front-loaded with no filler, but it is terse to the point of underspecification: 'on the page' is vague and the keyboard semantics are implicit. It is concise but not optimally structured to support correct invocation.

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 tool with no output schema and a required key parameter, the description does not explain how to format key values, whether modifiers are supported, or what the tool does after the key press. The destructiveHint marks risk without explaining when or why, leaving the agent to guess at invocation details.

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?

There is a single key parameter with 0% schema description coverage, and the description does not compensate: it never specifies accepted key names, casing, modifier syntax, or examples. 'Press a key' essentially restates the parameter name and tool purpose rather than adding usable parameter semantics.

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 uses a specific verb ('Press') with a clear resource ('a key'), which is enough to distinguish it from siblings like type, click, hover, and scroll. It is slightly ambiguous whether 'key' means a keyboard key or an on-page button, so it falls short of a 5.

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 guidance about when to choose press over type, click, or other sibling tools, and no mention of prerequisites such as focus or element state. The one-line description implies only the obvious use case and provides no exclusions or context.

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