pilot_hover

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

Discloses trigger events (hover states, tooltips), return type (confirmation with ref), and two error conditions (stale ref, timeout). No annotations provided, so extra burden carried well.

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?

Well-structured with sections for purpose, usage, parameters, returns, and errors. Some redundancy; could be slightly more concise but overall efficient.

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?

Covers essential aspects: purpose, when to use, parameter meaning, return value, and common errors. No output schema, so description compensates adequately.

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 100% (baseline 3). Description adds value by clarifying parameter format: 'Element reference from snapshot (e.g., @e7) or a CSS selector', explaining source and usage.

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?

Describes specific action (hover) and resource (element), with explicit triggering of hover states, tooltips, and dropdowns. Clearly distinguishes from sibling tools like click, fill, etc.

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?

States when to use: to reveal hidden content, trigger :hover, or inspect tooltip text. Lacks explicit when-not-to-use or alternatives, but sufficient for context.

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