Scroll web pages vertically by specified pixel amount to reveal content below the fold or navigate long pages. Set direction and distance for precise control.
Scroll page up or down by pixel amount. Use to reveal content below the fold or navigate long pages.
| Name | Required | Description | Default |
|---|---|---|---|
| tabId | Yes | Tab ID from create_tab | |
| amount | No | Pixels to scroll (default: 500) | |
| direction | Yes | Scroll direction |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It only states scrolling action and parameters, lacking details on animation, blocking, or return value.
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?
Two sentences, front-loaded with purpose, and efficient – no unnecessary 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?
The description is adequate for a simple scroll tool, but lacks differentiation from sibling tools like scroll_and_snapshot and does not specify if a return value exists.
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 coverage is 100%, and the description adds no extra meaning beyond what the schema provides for tabId, direction, and amount.
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 a page by pixel amount, specifying direction and default. It is distinct from element-scrolling siblings like camofox_scroll_element, though it doesn't explicitly differentiate.
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 tells when to use it ('reveal content below the fold or navigate long pages'), but does not mention when not to use or provide alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.