Hover element

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

Annotations already declare readOnlyHint=false and openWorldHint=true, and the description is consistent with that by noting hover can reveal menus/tooltips (i.e., it changes page state). It adds no detail on auto-waiting, scroll-into-view, what happens on timeout, or whether the hover persists before the next action—useful gaps given a mouse-state tool.

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?

A single sentence with the action front-loaded and the use cases trailing as a short example clause. Nothing is extraneous or buried.

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 three-parameter, fully documented, non-mutating interaction tool with no output schema, the description is nearly sufficient—only sequencing/timing behavior after the hover is left unstated, which the agent must infer.

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%, and the selector description already documents aria-ref, CSS, text, role, and XPath formats plus the frame/timeout semantics. The description adds nothing beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource ("Move the mouse over an element") that unambiguously identifies hover as distinct from click_element, fill_input, and select_option. It does not explicitly name a sibling or contrast itself, so it stops short of a 5.

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 parenthetical "e.g. to open a dropdown menu or reveal a tooltip" gives an implied when-to-use cue, but there is no guidance on when to prefer hover over click, whether to follow it with wait_for or get_page_snapshot, or any exclusions. Usage is inferable but not spelled out.

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