browser_hover

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

No annotations are provided, so the description carries the burden of explaining behavior. It clearly states the action of hovering, which is transparent enough for this simple tool, but it does not disclose edge-case behaviors such as whether the element must be visible or whether a wait is required.

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 sentence with no filler. The core action is front-loaded and the parenthetical adds practical context without bloat.

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 one-parameter hover action, the description is adequately complete. The output schema exists, so return values do not need to be explained. It could be slightly richer with caveats about element visibility or interaction timing, but those are not required for basic usage.

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 parameter 'selector' is fully documented in the schema as a CSS selector. The description adds no additional parameter-level semantics, which is acceptable given the schema already covers it.

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?

States a specific verb ('hover') and resource ('an element'), and clarifies the purpose with 'useful for dropdowns and tooltips.' This makes it immediately distinguishable from sibling actions like browser_click or browser_type.

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 gives clear context for when hover is appropriate: dropdowns and tooltips. It does not explicitly mention alternatives or when not to use it, but the use-case framing is sufficient for a simple interaction.

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