chrome_press_key

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Press a keyboard key' only states the action, omitting critical details such as where the key event is sent (active tab, focused element), whether modifiers are supported, and any preconditions like page focus. This is insufficient for safe invocation.

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 short sentence that is front-loaded and contains no redundant words. It is as concise as possible for the given purpose, though it sacrifices helpful context.

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 and full schema coverage, one might expect the description to be sufficient, but it lacks essential context about execution environment (active tab), behavior of modifiers, and the meaning of tab_index. The description is too minimal to fully inform an agent about the tool's effects and prerequisites.

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 100%, with each parameter clearly described (key examples, modifier enum, tab_index purpose). The description adds no information beyond the schema, so the baseline of 3 is appropriate.

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 'Press a keyboard key' uses a specific verb and resource, making the core action clear. However, it does not explicitly distinguish itself from sibling tools like chrome_type, which could also involve keyboard input, so it lacks explicit differentiation.

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?

There is no guidance on when to use this tool versus alternatives. No mention of use cases like keyboard shortcuts, single-key actions, or interactions with focused elements. The description provides no contextual cues for choosing this over chrome_type or chrome_click.

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