Hover

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

The description explains the immediate effect (moving the mouse and revealing hover menus) and does not contradict the annotations. It does not go into edge cases or side effects, but the primary behavior is transparent.

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, consisting of two clear sentences with no redundancy. It front-loads the core action and then provides the primary use case.

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 simple nature of the tool and the lack of an output schema, the description is sufficient for an agent to know when and how to invoke it. It could mention that it does not click, but this is implied by the contrast with browser_click.

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 schema already provides full descriptions for both parameters (target and element), so the tool description adds no additional parameter semantics. The baseline of 3 is appropriate since the schema covers all parameters.

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 the action ('Move the mouse over an element') and distinguishes it from clicking or dragging. It also specifies the purpose of revealing hover menus, making it easy to differentiate from sibling tools.

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 explicitly says to use it to reveal hover menus before clicking, giving a concrete use case. It does not explicitly mention alternatives like coordinate-based mouse movement, but the intended usage is clear enough for most scenarios.

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