browser_press

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

With no annotations, the description should disclose behaviors such as whether the browser must be focused, if key combinations work globally, or if there are side effects. It only gives examples, omitting details like handling of modifiers or system-level key press limitations.

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 extremely concise with two sentences and a list of examples. Every word is useful, and the structure is clear.

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 a single parameter and an output schema (not shown), the description is largely sufficient for the tool's simplicity. It could mention that it simulates a keyboard press in the active browser context, but the examples cover usage scenarios.

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?

Although schema coverage is 0%, the description provides concrete examples for the 'key' parameter (e.g., 'Enter', 'Control+a'), adding meaning beyond a plain string type. This helps the agent understand valid formats, though more comprehensive documentation would be needed.

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 'Press a keyboard key or key combination' and provides specific examples like 'Enter', 'Tab', 'Control+a'. It effectively distinguishes from sibling tools such as browser_click (mouse) and browser_type (text input).

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 guidance on when to use this tool versus alternatives like browser_type or browser_fill. Sibling tools exist for keyboard actions, but the description does not specify contexts where press is appropriate (e.g., pressing Tab to navigate) or when not to use it.

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