hover

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

No annotations are provided, so the description carries the full burden. It only restates the basic hover action and its intended effect, but does not disclose whether it moves the pointer permanently, whether it waits for menus to render, how failures are reported, or whether it changes UI state.

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, front-loaded sentence that clearly states the action and its purpose. It is not bloated, though the brevity comes at the cost of important behavioral and parameter detail.

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?

With no annotations, no output schema, four completely undocumented optional parameters, and no mention of return or failure behavior, the description is too sparse for the agent to invoke this tool reliably. The action is understandable, but the operational context is missing.

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 0% and the description provides no guidance for any of the four parameters (ref, scope, by_text, selector). The agent is left without any hint about which locator to choose or what the parameters mean, so the description fails to compensate for the schema's lack of documentation.

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 gives a clear verb and resource ('Hover over an element') and states the point of doing so ('reveal hover menus, tooltips, or submenus'). It is distinguishable from siblings like click and type, though it does not explicitly contrast itself with focus_element.

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 purpose clause implies when to use it: when the agent needs to surface hover-dependent UI. However, there is no explicit guidance about when not to use it or how it relates to alternatives such as click or focus_element.

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