browser_hover

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

With no annotations, the description carries full burden for behavioral traits. It only states the action and parameters, not disclosing side effects (e.g., triggering JavaScript events), whether it waits for hover effects, or behavior on failure. Minimal transparency.

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 with a clear one-line purpose followed by parameter and return descriptions in a structured docstring format. No redundant text, though the returns section could be integrated. Efficient use of space.

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 covers the basic purpose and parameters. An output schema exists, so the return mention is adequate. However, it omits context like requiring a prior snapshot, error handling, or behavioral nuances (e.g., hover duration). Acceptable but not thorough.

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%, so the description must compensate. It adds meaning by describing 'element' as a 'Human-readable element description' and 'ref' as 'Exact target element reference from the page snapshot.' This is helpful but still lacks details on format or how to obtain the ref.

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 'Hover over an element on the page,' specifying the action (hover) and target (element). It distinguishes from sibling tools like browser_click and browser_drag by implying a non-click action. However, it lacks explicit differentiation or scope details.

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 this tool versus alternatives (e.g., browser_click, browser_drag). It does not mention prerequisites, such as needing a page snapshot, or conditions like element visibility. No when-not-to-use information is given.

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