playwright_hover

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

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose what 'hover' entails (e.g., mouse simulation, potential side effects like triggering CSS events), error handling, or performance implications, leaving significant gaps.

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, direct sentence with zero waste—'Hover an element on the page' is front-loaded and efficiently conveys the core action without unnecessary words, making it highly concise and well-structured.

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 annotations, no output schema, and a simple but action-oriented tool, the description is incomplete. It lacks details on what hovering does (e.g., UI interactions), success/failure states, or integration with other Playwright tools, making it inadequate for full contextual understanding.

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%, with the selector parameter clearly documented in the schema. The description adds no additional meaning beyond implying the selector targets 'an element on the page', which is already covered. Baseline 3 is appropriate as the schema does the heavy lifting.

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 an element on the page' clearly states the action (hover) and target (an element), making the purpose immediately understandable. However, it doesn't distinguish this tool from its many sibling Playwright tools (like click, drag, etc.) beyond the specific action name, missing explicit differentiation.

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 like playwright_click or playwright_drag, nor does it mention prerequisites (e.g., requiring a page to be loaded). It's a standalone statement with no context for usage.

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