browser_press_key

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

Annotations indicate destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating action. However, the description adds no behavioral context beyond that, such as potential side effects like submitting forms or triggering navigation.

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, 'Press a key on the keyboard', which is front-loaded and free of unnecessary words. Every word earns its place, though it adds minimal information beyond the title.

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?

The tool is simple with one documented parameter and annotations, so the description is minimally sufficient. However, it lacks context about when to use this tool versus browser_type and does not mention potential side effects, leaving some gaps.

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 fully describes the 'key' parameter with examples like 'ArrowLeft' and 'a', giving 100% coverage. The description adds no additional parameter meaning, which is acceptable given the schema already documents it well.

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 tool presses a keyboard key, which is a specific verb+resource action. It distinguishes from mouse actions like browser_click and browser_hover, but does not explicitly differentiate from browser_type, which is for typing text.

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?

The description provides no guidance on when to use this tool versus alternatives such as browser_type or browser_click. There is no mention of scenarios where keyboard input is appropriate or when to avoid it.

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