browser_hover

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

With no annotations provided, the description carries the full burden of disclosing behavior, but it only restates the action in four words. It does not mention side effects like CSS hover states or UI changes, failure conditions, or whether the pointer remains positioned afterward.

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 compact and free of fluff, but it is more under-specified than concise, providing only a single sentence that states the action. It is usable but lacks the richness expected for a browser automation 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 2-parameter browser tool with no annotations and no output schema, this description is insufficient: it does not explain how to identify the element, when hovering is appropriate, or what observable effect the hover produces. An agent must infer these details from parameter names or sibling context.

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 baseline is 3; however, the schema descriptions ('Element reference', 'Element description') are thin, and the tool description adds no clarification on how to populate or relate the parameters.

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 states a clear action, 'Hover over element', with a specific verb and resource. It does not explicitly contrast with sibling tools like browser_click or browser_drag, but 'hover' is a distinct operation, so the purpose is apparent.

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 offers no guidance on when to use hover versus click, drag, or other sibling tools. It does not mention typical use cases such as revealing tooltips or hover states, nor any exclusions or alternatives.

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