browser_press

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

The description discloses the basic behavior (press a key) and gives examples of keys like 'Control+a' implying modifier support. However, it does not describe whether the key release is simulated, what happens if no element is focused, or if any side effects occur.

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 a clear one-sentence purpose followed by argument documentation. It avoids fluff but could benefit from slightly 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?

With no annotations and minimal description, the tool lacks a complete picture for an agent. The presence of an output schema reduces the need to document return values, but missing usage guidelines and behavioral details make it only moderately complete for a simple action.

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?

Despite 0% schema description coverage, the description adds meaning by providing concrete examples for the 'key' parameter (e.g., 'Enter', 'Control+a') and clarifies the 'session_id' parameter. This helps the agent understand valid inputs beyond the plain schema titles.

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' with specific verb and resource. It distinguishes from sibling tools like browser_type (types strings) and browser_click (clicks elements) by specifying a distinct action for keyboard keys.

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 is provided on when to use this tool versus alternatives (e.g., browser_type for text input, browser_click for mouse clicks). The description does not mention prerequisites or context such as needing an active element.

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