browser_press

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

No annotations are provided, so the description carries the full burden. It only says 'Press key' without disclosing any behavioral traits such as whether it triggers keydown/keyup events, requires a focused element, or has side effects like navigating or submitting forms. The schema example 'Control+a' hints at shortcuts but the description does not elaborate.

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 concise sentence with no superfluous words, and the action is front-loaded. It is appropriately sized for a simple tool, though it could include a bit more context without becoming verbose.

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 tool with no annotations, output schema, and many siblings, the description is incomplete. It does not explain what element receives the key press, whether a session is required, or how it differs from similar actions. While the schema covers parameters, behavioral and usage context are missing.

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 both 'key' and 'session' already described in the input schema. The tool description adds no additional parameter meaning beyond what the schema provides, so it meets the baseline of 3.

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 key (Enter, Tab, etc)' clearly states the verb (press) and resource (key) with concrete examples. It distinguishes this from most siblings like browser_click or browser_type, though it doesn't explicitly differentiate from browser_type (which types text) or browser_scroll. The purpose is unambiguous.

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 usage guidance is provided. The description does not mention when to use this tool over alternatives like browser_type or browser_click, nor does it describe any conditions or context (e.g., requires focus, works on current page). There is no exclusion or alternative routing.

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