hover

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

With no annotations, the description carries the full behavioral burden but discloses nothing: it does not say whether hovering waits, scrolls the element into view, triggers tooltips/menus, what force means, or how timeouts behave. It is not contradictory, but it is essentially silent on 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?

It is only two words, but this is under-specification rather than useful conciseness. There is no front-loaded context about what hovering does or how to invoke it correctly.

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 six-parameter browser automation tool with no annotations and no output schema, a two-word description is completely inadequate. An agent cannot determine targeting strategy, timeout behavior, or side effects from this definition.

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 coverage is moderate at 67%, with ref, tab, and selector documented in the schema, while force, timeout, and request_timeout are undocumented. The description adds no meaning beyond the schema and does not clarify targeting precedence between ref and selector.

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 names a specific verb and resource ('Hover an element'), so the basic action is clear. It does not distinguish hover from sibling element interactions such as click, drag, or scroll, and it gives no scope or intended effect.

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?

There is no guidance on when to use hover versus alternatives like click or find. No preconditions, no mention of how to target the element, and no exclusions are provided.

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