pressKey

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

No annotations are provided, so the description carries the burden. It states the core behavior (press key on focused element or page) but does not disclose nuances like the need to focus an element first if an id/selector is provided, or the behavior when no focus is specified. It also doesn't mention side effects or limitations. For a keyboard press tool, this is adequate but not rich.

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 a single clear sentence followed by a list of use cases. It is front-loaded with the purpose and contains no filler. Every sentence provides useful guidance.

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?

This is a simple tool with a well-documented schema and no output schema. The description covers main use cases and explains the focus behavior (on focused element or page). The schema covers parameter details. Together they give an agent sufficient context to invoke the tool correctly.

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 input schema describes all four parameters with 100% coverage. The description mentions examples like Ctrl+A, which hints at how modifiers and key combine, but it does not add substantive meaning beyond the schema. Baseline 3 is appropriate.

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 the tool presses a keyboard key on a focused element or page, and provides concrete use cases (Enter for form submission, Escape for dialogs, Tab/Arrow for navigation, Ctrl+A for shortcuts). This specific verb+resource distinguishes it from sibling tools like click (mouse) and type (text input).

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 lists scenarios where the tool is appropriate: form submission, closing dialogs, navigation, and shortcuts. This provides clear context for when to use it. It does not explicitly mention alternatives or when not to use it, but the examples make the intended use clear.

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