Browser press key

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

With no annotations, the description carries the burden. It discloses the core behavior (pressing a key) and the optional focusing step, but does not mention side effects, modifier keys, or whether keydown/keyup events are sent. Basic transparency 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?

One concise sentence that front-loads the action and includes the optional focusing behavior. Every word earns its place; no fluff.

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 simple action with no output schema and 3 straightforward parameters, the description is largely adequate. It covers the primary behavior and an optional precondition. Lacks explicit behavior on success/failure, but these are not critical for a key press tool.

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. It hints at 'key' and 'selector' ('focusing a selector'), but does not explicitly define parameters or mention session_id at all. The description adds minimal value beyond property names.

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 ('keyboard key') and context ('browser debug session'), and distinguishes from siblings by focusing on key events rather than clicks or typing. The optional selector focusing is an additional helpful detail.

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?

Implies usage in a browser debug session and mentions optional selector focusing, but does not explicitly state when to choose this over alternatives like browser_type or browser_click. No clear exclusions or alternative tool mentions.

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