browser_hover

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

It discloses human-like WindMouse movement, adding behavioral context beyond the schema. However, it does not mention potential side effects, prerequisites (e.g., element visibility), or return behavior.

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 concise, using three short sentences. It front-loads the action and includes the parameter explanation efficiently without wasted words.

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 a single parameter, no annotations, and an existing output schema, the description covers purpose, usage context, and parameter semantics adequately. It could be slightly more complete with error or timing details, but it is 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?

The description explicitly explains the only parameter 'selector' as a CSS selector for the target element, providing meaning absent from the schema (0% coverage).

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 clearly states it moves the mouse over an element using human-like movement, and distinguishes from siblings like browser_click by specifying its purpose (hovering).

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?

It mentions it is useful for triggering dropdowns or tooltips before clicking, giving a specific use case, but does not explicitly state when not to use or list alternatives.

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