browser_scroll

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so safety framing is covered; the description's useful addition is that bottom-scrolling triggers lazy loading of infinite lists. It says nothing about failure behavior when an element ref/selector is missing, or about the snapshot parameter's cost.

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 front-loaded sentence covering all three scroll modes with no filler or repetition.

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 six-optional-parameter tool with no output schema and full schema coverage, the description plus per-parameter docs are nearly sufficient. Only the interaction rules between ref/text/selector and the snapshot side effect are left implicit.

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%, with each of the six parameters individually described, so the schema carries the load. The description only restates the pixel and top/bottom modes and adds no precedence rules among ref/text/selector.

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 (Scroll) plus three distinct modes: by pixel delta, to top/bottom, and bringing an element into view. The parenthetical about infinite lists adds scope that separates it from browser_snapshot or browser_click.

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 'loads more of infinite lists' note gives a clear trigger for using it, and 'bring an element into view' implies the element-targeting mode. No explicit when-not-to-use or named alternative (e.g., browser_snapshot after scrolling) is offered.

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