browser_press_key

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

With no annotations, the description must fully disclose behavior, but it only states 'Press a key on the keyboard' without detailing whether it supports modifiers, global vs. focused element, or key release. This minimal information does not adequately inform the agent about side effects or 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 at one sentence, which is efficient but sacrifices clarity. While there is no fluff, the lack of detail makes it minimally viable rather than well-structured.

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 low complexity (one parameter, no output schema), the description is still incomplete. It does not explain what the key parameter expects, how the tool interacts with the browser, or what the outcome is, leaving significant gaps for correct invocation.

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 has one required 'key' parameter with no description, and the tool description adds no meaning about valid values (e.g., key names like 'Enter' or 'a'). With 0% schema description coverage, the description fails to compensate, leaving the agent uncertain about acceptable input.

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 'Press a key on the keyboard' clearly states the action (press) and resource (key on keyboard), distinguishing it from sibling tools like browser_click (clicking) and browser_type (typing text). However, it could be more precise by specifying that it simulates a single key press, but the core purpose is evident.

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 like browser_type or browser_click. There is no mention of prerequisites, key combinations, or typical scenarios, leaving the agent to infer usage from the name alone.

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