scroll

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

The description explains that direction is limited to specified values and amount is in wheel ticks with a default. However, it does not describe behavior at scroll boundaries, whether the scroll is smooth or instant, or any side effects. With no annotations, the description carries the full burden but is minimal.

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 sentence that is front-loaded with the tool's purpose and efficiently conveys all necessary parameter details without extraneous 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?

Given the simplicity of the tool and the existence of an output schema, the description covers the core functionality and parameter details. Minor gaps include lack of error handling or prerequisites like page load, but these are not critical for a basic scroll action.

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 lacks parameter descriptions (0% coverage). The description adds crucial meaning: direction values are explicitly listed as {up, down, left, right} and amount is defined as wheel ticks with a default of 3, which fully clarifies the parameter semantics.

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 tool scrolls the page and specifies the directions (up, down, left, right). It distinguishes itself from sibling tools like navigate, click, fill, etc., which have different purposes.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or limitations. Sibling tools are listed but no comparative context is given.

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