hover

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

With no annotations, the description carries the burden of explaining what the tool does. It discloses the hover action and the optional second click, and indicates that the click targets an element revealed by the hover. It does not detail waiting behavior, failure conditions, or whether the hover must be on a visible element, but the core side effect is accurately represented.

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 front-loaded: the action and optional follow-up are stated first, followed by a brief example and compact parameter explanations. Every sentence contributes useful information with no padding.

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?

Given this is a simple two-parameter browser action with an output schema available, the description covers the invocation pattern and both parameters. It does not detail edge cases like non-revealing hovers or timeout behavior, but for this tool's complexity the guidance is sufficiently complete.

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, and it does. It explains selector as 'Element to hover over' and then_click_selector as 'If given, click this element after hovering,' adding meaning that the schema titles alone do not provide. It stops short of specifying selector syntax, but the semantics for both parameters are clear.

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 a specific action: simulate a mouse hover over an element, with the optional follow-up of clicking a second element revealed by the hover. The dropdown example grounds the use case and distinguishes it from sibling tools like click and drag_and_drop.

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 to use this tool: when an element requires hovering to reveal another element, e.g. a dropdown menu item. It does not explicitly mention alternatives or when not to use hover, but the conditional then_click_selector behavior effectively communicates the intended pattern.

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