browser_scroll

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

No annotations are provided, so the description carries the full burden. It says the tool scrolls a page, but does not disclose what constitutes a page, whether scrolling is immediate or smooth, behavior at page boundaries, defaults for omitted parameters, or any return information.

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?

A single compact sentence with no wasted wording. The action and scope are front-loaded immediately.

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 UI-action tool with no annotations, no output schema, and no parameter descriptions in the schema, the one-sentence description leaves important gaps. An agent cannot confidently infer defaults, valid direction strings, or page-size behavior.

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 0%, so the description must compensate. It clarifies that pages refers to number of pages and direction refers to up or down, but does not specify valid direction values, whether pages accepts negative or fractional values, or what happens when either optional parameter is omitted.

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?

States a specific verb and resource: scroll the page up or down by a number of pages. The browser context is clear from the tool name and page wording, though it does not explicitly differentiate itself from platform-specific siblings such as mac_scroll or phone_swipe.

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?

Provides no guidance on when to use this tool versus alternatives such as browser_read, browser_snapshot, or mac_scroll. It also does not mention prerequisites, expected page context, or when scrolling is preferable to navigation.

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