cdp_hover

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action ('hover') without mentioning whether the element needs to be visible, whether hover events are triggered, any side effects, or failure behavior. This minimal information does not adequately disclose the tool's runtime behavior.

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 that states exactly what the tool does with no filler or redundancy. It is front-loaded with the core action and target, making it easy to parse.

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?

The description is adequate for a simple hover action, but it lacks context about return values, error conditions, or prerequisite states (e.g., element presence). Given the absence of annotations and output schema, it only minimally fulfills the completeness requirement, leaving the agent without full operational context.

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?

The description clarifies the 'selector' parameter by specifying it is a CSS selector, which is not otherwise described in the schema. Since schema coverage is 50% (session_id is described), the description adds meaningful value for the otherwise undocumented parameter, though it does not elaborate on session_id beyond 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 uses a specific verb ('Hover') and a specific resource ('an element matched by CSS selector'), clearly distinguishing it from sibling tools like cdp_click or cdp_mouse_move. It precisely states the action and target in a single concise sentence.

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 about when to use this tool versus alternatives such as cdp_mouse_move or cdp_click. The description neither states explicit usage context nor mentions any exclusions, leaving the agent without information on tool selection.

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