press_key

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

No annotations are provided, so the description carries full burden. It discloses a key behavioral trait: after pressing the key, it returns a new snapshot. However, it does not mention side effects, whether it waits for navigation/load, or how session state is affected, leaving gaps for a mutation-like tool.

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 concise and well-structured: a one-sentence purpose statement followed by a clear Args list. No wasted words, and the key information is 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 its simplicity (2 params, output schema present), the description covers the essential aspects: what the tool does, its arguments, and the return behavior (new snapshot). It does not explain when to use vs. alternatives, but that is the usage dimension, and the output schema covers return value 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?

Schema description coverage is 0%, but the description compensates by explicitly explaining each parameter: 'keys' is a key or chord to send with a formatting example, and 'session_id' is the session to act on with a default value. This adds meaningful meaning beyond the raw 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?

The description uses a specific verb ('Press') and resource ('a key or chord') with concrete examples ('Enter', 'Control+a'), and clearly distinguishes itself from siblings like type_text (typing strings) and click (mouse actions) by explaining it sends keyboard keys and then returns a new snapshot.

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?

No guidance on when to use this tool versus alternatives. It does not mention using this for keyboard shortcuts/hotkeys vs. type_text for text entry, nor does it note any prerequisites like needing an active session or focus.

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