browser_hover

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

With no annotations, the description carries the full burden, but it only states 'Hover over an element.' It does not disclose whether this simulates a real mouse move, whether it dispatches events like mouseover/mouseenter, or whether it waits for the element to be visible. The behavior is under-specified.

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, consisting of a single sentence with no filler. However, it is so brief that it borders on under-specification, which slightly reduces the score from 5.

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 large number of sibling tools and the lack of output schema, the description leaves significant gaps. It does not explain what the tool returns (if anything), how it interacts with the page state, or how it differs from other mouse-related actions. The minimal description is insufficient for a tool in such a complex context.

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 parameter 'selector' is fully documented in the schema (CSS selector), so the description adds no additional semantic value. This matches the baseline for 100% schema coverage, as the schema already clarifies the parameter format.

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 an element' clearly identifies the action (hovering) and the resource (an element), distinguishing it from siblings like click or type. It is specific but could be slightly more explicit about the target being a DOM element in the browser context.

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 such as browser_click or browser_double_click. There is no mention of hover being used to trigger tooltips or dropdown menus, nor any exclusions or prerequisites.

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