scroll

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

No annotations exist, so the description bears full responsibility. It discloses the action (scroll) but omits behavioral details like whether it simulates touch gestures, whether it scrolls the entire page or a focused element, or what happens when scrolling to an edge. Minimal value added.

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 extremely concise (single sentence). While it wastes no words, it lacks structure and could benefit from a second sentence about usage context or parameter guidance. Front-loaded verb is fine.

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?

With 27 parameters and no output schema, the description provides insufficient context for an agent to confidently select and invoke the tool. It does not explain parameter interactions, the difference between scroll and swipe, or expected outcomes. The tool's complexity demands more context.

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 96%, so the input schema already documents most parameters thoroughly. The description adds no parameter-specific guidance (e.g., when to use 'pixels' vs 'amount' vs 'durationMs'). Baseline 3 is appropriate as the schema does the heavy lifting.

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 in a direction or to an edge' clearly specifies the verb (scroll) and the resource (implicit view), and matches the direction parameter enum that includes directional and edge values. However, it does not distinguish from sibling tools like 'swipe', leaving ambiguity about when to use which.

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 usage guidelines are provided. The description does not indicate when to use scroll vs alternatives, nor does it mention prerequisites or limitations such as requiring a scrollable viewport.

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