computer_scroll

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

No annotations are provided, so the description carries the burden. It discloses that amount can be omitted or 0 for driver default, and that it returns a JSON response. However, it doesn't disclose whether scrolling is relative to current position, whether it requires permissions, or what happens on invalid direction values.

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 compact and front-loaded with the core action. The Args section is clear and each parameter gets a one-line explanation. The Returns line is minimal but sufficient. No wasted 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?

For a simple 3-parameter tool with an output schema, the description covers the essentials. It lacks edge-case behavior (e.g., what if direction is invalid, what if serialno is wrong) and doesn't mention any prerequisites beyond serialno from list_devices. Given the tool's simplicity, this is adequate but not rich.

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 0%, so the description must compensate. It does: it explains serialno comes from list_devices, direction is one of up/down/left/right, and amount is wheel steps with a default behavior. This adds meaning beyond the bare 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 states a specific verb and resource: 'Scroll the mouse wheel' on a computer device. It distinguishes itself from siblings like computer_move and computer_click by focusing on wheel scrolling, though it doesn't explicitly name a sibling alternative.

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 implies usage context: it's for scrolling a mouse wheel on a computer device, with serialno from list_devices. It doesn't explicitly state when to use this over alternatives like computer_move or mobile_swipe, but the 'from list_devices' hint gives some context.

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