browser_hover

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

Annotations already indicate this is not read-only and is marked destructive, but the description itself adds no behavioral context. It doesn't warn that hovering may trigger JavaScript events, alter page state, or require permission. No contradiction, but no enrichment beyond annotations either.

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 short sentence with the action front-loaded. There is no filler or redundant wording; it is appropriately minimal for a simple tool.

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 with a required target, the description plus schema is mostly adequate. However, the destructiveHint annotation suggests side effects that the description never explains, and there is no output-schema or return-value note. Minor gaps remain.

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% and both parameters (target and element) are clearly documented in the schema. The description's 'element on page' loosely maps to the target parameter but adds no syntax, format, or extra meaning beyond the schema.

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 ('hover') and resource ('element on page'), which clearly conveys the core action. It doesn't explicitly differentiate from siblings like browser_click or browser_drop, but the verb is distinct enough to avoid confusion.

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 use case is implied by the verb: use this when you need to hover over an element. However, the description provides no explicit guidance on when to choose hover over click, drag, or drop, and it mentions no exclusions or prerequisites.

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