mouse

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions scrolling and dragging but omits side effects, target device behavior, scroll direction, duration effects, and any permission or safety context.

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 a single front-loaded sentence with no redundant text. However, it is too terse for an eight-parameter input tool and omits information that would make the sentence useful rather than merely short.

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?

This is a complex input tool with eight parameters, no annotations, and no output schema. The description identifies the high-level actions and coordinate basis, but it is not complete enough to guide correct invocation across the various parameters.

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% across eight parameters. The phrase 'absolute coordinates' gives some context for the coordinate fields, but the description does not explain x/y versus to_x/to_y, delta, device, duration_ms, or the required action enum.

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 two specific operations, scrolling and dragging, and clarifies that drag uses absolute coordinates. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling click or keyboard 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?

There is no guidance on when to choose scroll versus drag, no prerequisites, and no mention of alternatives such as click. The description only implies that the tool is used for these two mouse actions.

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