browser_press_key

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

Annotations note destructiveHint and openWorldHint, but the description adds no behavioral context beyond 'press a key'. It does not mention that key presses can trigger page events, affect focus, or what happens with invalid key values.

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?

One sentence, no wasted words. The description is appropriately sized for a simple tool with one parameter.

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 simple tool with one param and no output schema, the description is minimally adequate. However, it lacks mention of the context (e.g., presses on focused element, vs browser_type) which slightly reduces completeness.

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?

The input schema covers the single 'key' parameter with helpful examples (e.g., ArrowLeft, a). Since schema coverage is 100%, the description adds no additional parameter info. Baseline 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 clearly states the action ('press') and resource ('key'), but it does not differentiate from sibling tools like 'browser_type' which types a sequence. Adding 'single key' would improve distinction.

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 (e.g., 'browser_type' for multiple characters, 'browser_fill_form' for forms). No exclusions or context provided.

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