vnc_mouse_scroll

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

With no annotations, the description carries full burden but discloses nothing about behavior, side effects, or safety. 'Scroll the mouse' is almost tautological and does not explain whether it scrolls the wheel, moves a scrollbar, or has any cumulative effects.

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?

Three words is very short, but this is under-specification, not effective conciseness. The description does not convey enough information to be useful, so it fails to 'earn its place.'

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 two-parameter tool without an output schema, the description still omits key context like how the scroll is performed (e.g., wheel events) and the meaning of the default amount. This leaves the tool underspecified.

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%, yet the description does not compensate by explaining 'direction' or 'amount'. It adds no meaning beyond the schema field names, leaving the agent without semantics for these parameters.

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 'Scroll the mouse' uses a specific verb and resource, and clearly distinguishes from sibling tools like vnc_mouse_move, vnc_mouse_drag, and vnc_mouse_click. However, it lacks explicit mention of the wheel or direction, making it slightly ambiguous.

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 is provided on when to use this tool versus alternatives like vnc_mouse_move or vnc_mouse_drag. There is no mention of prerequisites, typical scenarios, or exclusions.

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