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 of behavioral disclosure. However, it only says 'press key' and does not mention what happens when pressing, whether it triggers events, requires focus, or has side effects. This is entirely opaque.

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?

While the description is short, it is severely under-specified. A single word '按键' does not provide enough context to be considered appropriately concise; it omits critical information and is not front-loaded with useful content.

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 the tool has two required parameters, no output schema, and no annotations, the description must explain context, return behavior, and usage. It does none of this, making it completely inadequate for an agent to correctly invoke the tool.

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 0%, and the description adds no meaning to the parameters 'key' and 'selector'. It does not explain what format 'key' should be (e.g., 'Enter', 'a') or what 'selector' targets. The description fails to compensate for the lack of schema documentation.

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 '按键' translates to 'press key', which does convey a verb and resource but is extremely vague. It does not specify what is pressed (keyboard key vs mouse) or how this tool differs from siblings like browser_keyboard_down, browser_type, or browser_click. The purpose is minimally discernible but lacks necessary details for selection.

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 the many sibling tools that also involve keyboard or mouse actions. There is no mention of context, alternatives, or prerequisites.

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