browser_hover

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

Annotations indicate readOnlyHint=false and destructiveHint=true, which is surprising for a hover action, but the description adds no context about side effects, timing, or whether hover can trigger navigation or state changes. The description does not go beyond the obvious act of hovering, leaving behavioral ambiguity.

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 with no wasted words, making it easy to scan. However, it is arguably too terse to fully convey the tool's purpose and usage context, though conciseness itself is strong.

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 hover action, the description is minimal, but the annotations (destructiveHint=true) and lack of output schema create a need for additional behavioral context. The description does not explain what happens after hovering, potential delays, or failure conditions, leaving the agent under-informed for a tool that could have side effects.

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 100%, with both 'target' and 'element' described in the schema. The description itself adds no parameter details, but because the schema fully documents parameters, a baseline score of 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 'Hover over element on page' uses a specific verb (hover) and resource (element on page), clearly distinguishing it from sibling tools like browser_click, browser_drag, and browser_drop. It is immediately obvious what action this tool performs.

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 when hovering is needed to trigger tooltips or reveal menus. No exclusions or prerequisites are mentioned, so an agent must infer usage solely from the name.

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