browser_press_key

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions pressing a key or chord but does not explain side effects (e.g., triggering keydown/input events), whether it focuses the element first, or if it requires a selected element. This is a significant transparency gap for a tool that can alter page state.

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 a single, front-loaded sentence with no redundant words. Every word earns its place, conveying the action and target efficiently.

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 tool is simple but lacks annotations and output schema. The description does not mention return value, session requirements, or behavior when no selector is provided. For a mutation-like action, more context (e.g., how to specify chords, whether it works without a focused element) is needed; the minimal description leaves important gaps.

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 33% (only sessionId has an inline description). The tool description adds meaning to 'key' as a keyboard key/chord and to 'selector' via 'selected element', but does not provide syntax examples or clarify behavior when selector is omitted. It partially compensates for the schema's low coverage.

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 verb 'Press' and the resource 'keyboard key or chord', with optional 'selected element' scope. This distinguishes it from sibling tools like browser_click (mouse) and browser_fill (text input), providing specific action and target.

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 explicit guidance on when to use this tool versus alternatives. The description implies keyboard interaction but does not state when to choose it over sibling tools, nor prerequisites (e.g., active session, focused element).

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