Scroll with the wheel

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

The description says it dispatches a wheel event and mentions it is a synthetic scroll animation, which gives some insight into behavior. The readOnlyHint=false annotation indicates state mutation, though the description itself could more explicitly state that scrolling will occur.

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 concise, using only two sentences with no redundant information, and the structure directly states the action and the recommendation.

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 includes a reference to browser_scroll, providing context for when this tool is useful versus the alternative, and is sufficiently complete for a simple scroll action without needing to specify return values or error handling.

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?

Both parameters are clearly explained: deltaX as horizontal scroll delta in pixels, and deltaY as vertical scroll delta with positive meaning downward, adding meaningful detail beyond the parameter names.

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 that the tool dispatches a wheel event and explicitly recommends browser_scroll as a preferred alternative, making the purpose unambiguous and differentiating it from related 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 direct usage guidance by advising to prefer browser_scroll for a single round-trip instead of a synthetic scroll animation, giving clear situational direction.

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