mouse_scroll

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

The description discloses the effect of moving the mouse to x,y before scrolling, which is a behavioral side effect. Annotations are neutral, so this adds value. However, it does not mention potential failure cases or permissions required.

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 three concise sentences: purpose, arguments, return. Front-loaded with the main action. No unnecessary words.

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 covers core behavior and return value, supplemented by schema details. With an output schema present, the return is adequately specified. It omits edge cases (e.g., invalid coordinates) but is complete for a simple scrolling tool.

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 already provides clear descriptions for amount (scroll clicks, up/down) and x,y (move before scrolling). The description repeats 'positive up / negative down' and 'optional position', adding minimal new info beyond the schema.

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 action 'scroll the mouse wheel vertically' with explicit parameters for amount (positive up, negative down) and optional position. It distinguishes from siblings like mouse_click or mouse_drag by specifying vertical scrolling.

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?

No guidance on when to use this tool versus alternatives such as mouse_drag or mouse_move. The description lacks when-not-to-use or prerequisites, leaving the agent to infer usage from the name alone.

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