Wheel

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

The description mentions behavioral effects (zoom with Control, horizonal scroll) but does not elaborate on default behavior, such as what happens without modifiers (vertical scroll) or event dispatching details. Given no annotations, this is adequate but leaves some ambiguity.

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 two sentences, front-loading the primary action. Every word serves a purpose, with no redundancy or filler. It efficiently conveys both the core function and primary use cases.

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 the tool's simplicity and the presence of sibling tools like 'scroll' and 'scroll_to', the description adequately captures its distinct purpose. However, it does not explicitly differentiate from those tools or explain the return value, though this is minor for an event dispatch action.

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 schema covers 100% of parameters, so baseline is 3. The description adds context by mentioning 'Control modifier' and 'horizontal scrolling,' which relate to parameters 'modifiers' and 'deltaX', but does not provide additional semantic details beyond what the schema already documents.

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 clearly states the tool dispatches a mouse wheel event at specific coordinates, with explicit use cases for scroll-to-zoom and horizontal scrolling. This distinguishes it from sibling tools like 'scroll' and 'scroll_to' by specifying the exact event type and coordinate-based nature.

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 two explicit use cases: 'scroll-to-zoom (with Control modifier)' and 'horizontal scrolling'. It implies when these scenarios apply but does not explicitly state when not to use this tool or mention alternatives like 'scroll' or 'hover'.

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