scroll

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

No annotations are present, so the description carries the full burden of explaining behavior. It mentions scrolling direction and edges but omits key behavioral details such as whether scrolling is animated, whether it can settle, or what the response contains. The schema's settle parameter suggests a diff-return behavior, but the description does not disclose this.

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 that directly states the core functionality. No filler or redundant information is present.

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?

Despite the high schema coverage, the tool has no output schema and no annotations, and the description is too terse to fully convey expected behavior or return values. It does not mention the settle/diff capability or how scrolling amounts are determined, leaving gaps for an agent deciding whether to invoke it.

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 97%, so the baseline is 3. The description adds minor value by clarifying that 'top' and 'bottom' refer to edges of scrollable content, which the schema does not explicitly state. However, it does not explain interaction with other parameters like amount or pixels.

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 uses the specific verb 'scroll' and identifies the resource as 'scrollable content,' making the action clear. It also distinguishes between directional scrolling and scrolling to the top/bottom edge, which is a meaningful scope. However, it does not explicitly contrast with sibling tools like 'swipe', so it misses a clear differentiation point.

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 like 'swipe' or 'gesture'. It simply states what the tool does, leaving usage context implied but never explicit.

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