browser_hover

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

With no annotations, the description must disclose behavioral traits. It only says the pointer hovers over an element, but omits whether hover events are triggered, whether the element must be visible, whether the action is synchronous, or any side effects. This is minimal for an interactive action.

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 a single, short sentence with no fluff. It is front-loaded and conveys the core action and target efficiently.

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 tool with one simple parameter and no output schema, the description is incomplete. An agent needs to know how to obtain a valid ref (e.g., from browser_snapshot), whether the element must be in view, and what happens after hovering. Without this, the tool may be misused.

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 has a single 'ref' parameter with 0% coverage. The description says 'by ref' but does not explain what a 'ref' is, how to obtain it, or its format. This adds minimal meaning beyond the parameter name and leaves the agent guessing about the required value.

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 (hover), the target (element), and the mechanism (by ref). While it doesn't explicitly contrast with siblings like browser_click or browser_drag, the verb 'hover' is unambiguous and distinct enough for an agent to infer its purpose.

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?

No guidance is provided on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., needing a ref from a prior snapshot), when hover is preferred over click or drag, or any exclusion conditions.

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