Hover over a DOM element by providing a CSS selector and optional tab index, enabling interactive testing in Arc Browser.
指定したセレクタの要素にホバーする
| Name | Required | Description | Default |
|---|---|---|---|
| selector | Yes | CSSセレクタ | |
| tab_index | No | タブのインデックス（指定しない場合はアクティブタブ） |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description merely says 'hover' without disclosing behavioral details such as whether it triggers events, waits for animations, or requires the element to be visible. No annotations are provided to compensate.
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 a single concise sentence, but it is somewhat terse. It could be slightly more informative without losing conciseness.
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 only two parameters and no output schema, the description is minimally adequate but could mention typical behavior like triggering CSS :hover or emitting events.
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 coverage is 100%, and the description does not add additional meaning beyond the parameter descriptions already provided in 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 'Hover over the element of the specified selector' clearly states the action (hover) and the target (element by CSS selector), distinguishing it from sibling tools like arc_click or arc_drag.
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 guidance is provided on when to use hover versus alternatives like click or drag. The description does not mention prerequisites or conditions for use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.