browser_press

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

Annotations (openWorldHint: true, destructiveHint: false) already indicate side-effect potential and safety. Description does not add details beyond the basic action, such as focus requirements or possible side effects.

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?

Two concise sentences, front-loaded with purpose and a clear alternative reference, no redundancy.

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?

Adequate for a simple action: mentions single key press, alternative for typing, and optional selector. Could mention if keys cause navigation or default actions, but overall sufficient.

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 covers both parameters with descriptions; description adds concrete examples for 'key' (e.g., Enter, Escape), enhancing clarity beyond schema.

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?

Clearly states it presses a single key on the page, with examples (Enter, Escape, Tab, ArrowDown), and explicitly distinguishes from browser_type 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?

Provides clear context for use (pressing single keys) and mentions browser_type as alternative for typing, but lacks explicit when-not-to-use or eligibility criteria.

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