browser_scroll

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

With no annotations provided, the description must disclose behavioral traits. It only states 'Scroll the page in a direction,' but does not specify how scrolling is performed (e.g., instant vs animated, viewport vs element), nor does it mention the optional 'selector' parameter that changes behavior. This omission reduces transparency.

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, concise sentence with no unnecessary words. It is appropriately front-loaded and effectively communicates the core action without redundancy.

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?

For a simple scrolling tool with no output schema, the description provides the essential purpose but lacks details about return behavior or optional use cases like element-specific scrolling. It is minimally complete but could be improved by mentioning that no value is returned or that it scrolls the main page by default.

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 has 100% coverage, describing all three parameters (amount, selector, direction) with descriptions. The tool description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 the page in a direction' clearly identifies the action (scroll) and resource (the page), and is distinct from sibling tools like browser_click or browser_navigate. However, it could be more specific by mentioning that scrolling can be within a specific element via the 'selector' parameter.

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 guidance is provided on when to use this tool vs alternatives like browser_wait (which might wait for scroll events) or browser_execute_js (which could implement custom scrolling). The description does not mention prerequisites or contextual cues for selecting this tool.

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