safari_hover

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

No annotations exist, so the description must carry behavioral info. It merely states the action without disclosing side effects, safety, or timing. For a hover operation, likely nondestructive, but unstated.

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?

Description is extremely concise and front-loaded, with every word necessary. No filler. Could be slightly expanded for completeness, but structure is effective.

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 no output schema and no annotations, the description is too minimal. It lacks information on return behavior, error cases, or prerequisites (e.g., page must have DOM). For a simple hover tool, it's barely adequate.

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%, and the description summarizes the parameter groups (ref, selector, x/y). It adds no new meaning beyond what the schema already provides, meeting the baseline but not exceeding.

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 explicitly states the action ('hover over element') and the three methods (ref, selector, x/y), clearly distinguishing from sibling tools like 'safari_click' or 'safari_double_click'.

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 implies usage by listing methods but provides no explicit guidance on when to use this tool versus alternatives like 'safari_native_hover' or 'safari_click'. No context about prerequisites or when not to use.

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