browser_hover

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

The description adds no behavioral information beyond the annotations already provided. Annotations indicate destructiveHint=true, but the description doesn't explain potential side effects like triggering mouseover events or requiring element visibility. It simply restates the action.

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 concise sentence, 'Hover over element on page', with no redundant words. It is appropriately front-loaded and easy to parse, though sparse in 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?

For a simple hover action, the description combined with rich schema and annotations is mostly adequate. However, it lacks context about when to use this tool and potential side effects, leaving some gaps in understanding the full implications of the action.

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 having meaningful descriptions. The tool description itself adds no parameter information, but the schema already provides sufficient meaning, justifying the baseline score of 3.

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' clearly states the action (hover) and the target (element on page). It distinguishes itself from sibling tools like browser_click and browser_drag by naming the specific hover operation.

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 hover versus other interaction tools (e.g., click, drag), nor any prerequisites such as obtaining a page snapshot first. The description gives no context for selecting this tool over alternatives.

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