hover

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

No annotations exist, so the description carries full responsibility for behavioral disclosure. It fails to mention whether the action triggers hover events, requires the element to be visible/interactive, or has any side effects. This is a significant gap for an interaction tool.

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 extremely short (4 words), but it is under-specified rather than concise. It lacks necessary details that a longer description should include, such as parameter semantics and usage context.

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 the lack of annotations, output schema, and the presence of many sibling interaction tools, the description is incomplete. It does not explain the tool's relationship to click, scroll, or other actions, nor does it clarify what happens after a hover (e.g., triggering tooltips or state changes).

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?

With 0% schema description coverage, the description must add meaning to the 'selector' parameter. It provides none—no format guidance (CSS, XPath, text), no examples, and no hint about what selectors are valid. The tool effectively has no documentation for its only parameter.

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 'Hover over an element' clearly states the action and resource (hovering over an element). It is a specific verb-resource combination. However, it does not differentiate from sibling tools like click or scroll, which also act on elements.

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?

No usage guidelines are provided. The description does not specify when to use hover over alternative interactions like click or scroll, nor does it mention any prerequisites or exclusions.

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