browser_hover

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action and tab targeting but does not describe side effects like triggering hover states, tooltips, or menu expansions, nor does it mention visibility requirements or whether the hover completes synchronously.

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 short and front-loaded: the core action appears first, followed by the tab-targeting detail. Both sentences are informative and there is no filler, though a brief usage note could be added without harming brevity.

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 simple hover action, the description plus a fully documented schema is close to minimally viable. However, there is no mention of when hover is useful, what the expected outcome is, or which parameter (ref vs element) is authoritative, leaving some context for the agent to infer.

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 100%, so the parameters are already fully documented. The description adds only that tab targeting is supported, which duplicates the tabId schema description rather than providing new semantic insight.

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 uses a specific verb ('Hover') and resource ('an element'), making the tool's action unambiguous. It also mentions tab targeting, which helps distinguish it from related browser interaction tools like browser_click or browser_press_key.

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 provides no guidance on when to use hover instead of alternatives, such as when revealing tooltips or dropdown menus before a click. It does not mention any hover-then-act pattern or conditions that would make hover the appropriate sibling tool.

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