session_press

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

No annotations are provided, so the description carries the full behavioral burden. It only says a key is pressed; it does not disclose possible side effects like form submission or navigation, whether the element is focused first, keydown/keyup behavior, or what the outcome/return value looks like.

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 concise sentence that is front-loaded with the verb and packs useful examples in parentheses. There is no filler or repetition.

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?

With no output schema, no annotations, and four parameters where three lack schema descriptions, the description is too thin. It does not explain how to populate key, tabId, selector, or ref correctly, nor what an agent should expect after invoking it.

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 only 25%, so the description must compensate. It adds valid-key examples and a sense of targeting, but it leaves key semantics, tabId, and selector behavior undocumented and does not clarify the relationship between ref, selector, and tabId.

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 ('Press') and resource ('keyboard key') with examples, and identifies the target as focused or specific element. This generally distinguishes it from mouse/text siblings like session_click and session_type, though it doesn't name them 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?

The examples (Enter, Tab, Escape) imply it is for special-key presses, and 'on the focused element or a specific element' gives targeting context. However, there is no explicit when-to-use/when-not-to-use guidance or mention of alternatives such as session_type for text input.

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