session_key_press

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

There are no annotations, so the description carries the burden of explaining behavior. It discloses that the action runs on the active session tab and requires an existing session, but it does not explain possible side effects of the keys, whether the page state changes, or what the returned result contains.

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, direct, and front-loaded with the action and examples. There is no filler or redundant restating of the tool name.

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?

The core action and session prerequisite are present, and the output schema reduces the need to explain return values. However, the mysterious max_chars parameter and the lack of any side-effect disclosure keep this from being contextually complete.

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%, so the description must compensate for the schema. It provides useful semantics for the required key parameter by listing valid keyboard names, but max_chars is completely unexplained. An agent cannot infer why max_chars defaults to 6000 or how it affects this key-press operation.

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 identifies a specific action (press a key), a specific resource (the active tab of a session), and lists concrete accepted key names such as 'Enter', 'Escape', 'Tab', 'ArrowDown', and 'F5'. This clearly distinguishes it from sibling tools like session_click, session_type, and session_scroll.

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 explicitly states the prerequisite 'Requires session_start', which is a clear usage constraint. It also signals that the tool is intended for sending special/shortcut keys through the active session tab. It does not explicitly name alternatives or exclusions, but the context is sufficiently clear.

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