browser_press_key

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

With no annotations, the description carries the full burden. It only says 'Press a keyboard key' and 'Returns an updated snapshot,' lacking details on focus requirements, key validity, or underlying DOM events. This is insufficient for a mutating action.

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: two sentences plus an Args list. The action is front-loaded, and every sentence serves a purpose. No redundant information.

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 the tool's simplicity, the description covers basic purpose and parameters. It mentions return of an updated snapshot but omits context like focus requirements or behavior with modifiers. Completeness is adequate but not thorough.

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 coverage is 0%, so the description must add meaning. It clarifies page_id as 'Target page ID' and key as 'Key name (DOM KeyboardEvent key)', providing useful context beyond the schema's minimal type/title. However, it could specify exact key format.

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 action: 'Press a keyboard key' with examples such as Enter, Tab, Escape, etc. It distinguishes this tool from siblings like browser_click and browser_type by specifying key presses.

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 implies usage for sending special keyboard keys but does not explicitly state when to use this tool over alternatives like browser_type or browser_click. No exclusions or prerequisites are mentioned.

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