Scroll the page

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

The description discloses that the operation is a single round-trip and reports whether the end was reached, adding useful behavioral detail beyond the minimal annotations. It does not contradict readOnlyHint or destructiveHint, though it could mention side effects more explicitly.

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 very concise and front-loaded with the core purpose. Every sentence adds meaningful information about behavior or output.

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 covers the main action, target scope, round-trip nature, and outcome reporting. It does not specify the exact return shape, but for a simple scroll tool the statement that it reports whether the end was hit is probably sufficient.

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?

All five parameters already have clear descriptions in the schema, including defaults and the override behavior of x/y over direction. The description adds little beyond the schema, so it meets the baseline but does not elevate the semantic guidance.

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 the page or an element, and the title reinforces this. It distinguishes itself from browser_mouse_wheel by noting it is a single round-trip with no synthetic wheel events.

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 does not explicitly indicate when to choose this tool over alternatives such as browser_mouse_wheel or browser_mouse_drag_xy. It mentions no synthetic wheel events, but does not explain why an agent should prefer this tool in a given situation.

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