hover

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

The description is extremely brief and does not disclose behavioral traits beyond the basic action. There are no annotations to compensate. An agent would not know if hovering triggers events, requires a page to be loaded, affects state, or is a safe operation. The description fails to provide necessary context for safe invocation.

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 sentence and is concise. However, it is under-specified for the complexity of the tool. It avoids redundant information but sacrifices clarity. Every word earns its place, but additional context would improve usability without bloating it.

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 should provide more detail about return values, error scenarios, and behavioral side effects. It is insufficient for an agent to fully understand the tool's implications. The three parameters with complex constraints are not explained in the description itself.

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 input schema has 100% coverage for parameter descriptions, so the baseline is 3. The tool description adds no additional meaning beyond the schema, which already explains the parameters and their constraints (e.g., exactly one of selector|ref). Thus, no extra value is provided.

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 primary action (hover) and the target (element). It is a specific verb+resource combination that distinguishes it from siblings like 'click' or 'type'. However, it lacks explicit differentiation from other element interaction tools.

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 provides no guidance on when to use this tool versus alternatives such as 'click' or 'press'. It does not specify if hover is meant for triggering CSS hover effects, tooltip previews, or other interactions, nor does it mention any prerequisites or when not to use it.

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