browser_scroll

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

With no annotations, the description must carry the full burden of behavioral disclosure. It mentions the optional target behavior but does not explain deltaX/deltaY semantics (relative vs absolute), what happens when both target and deltas are supplied, or any side effects like scroll events. This leaves significant behavioral ambiguity.

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 sentence that is direct and front-loaded, with no filler words. It effectively communicates the core purpose in minimal space.

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 tool has five parameters, no output schema, and no annotations, yet the description is very sparse. It fails to explain how deltaX/deltaY work, how target interacts with these deltas, or what the return value is, leaving the tool under-specified for its complexity.

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 schema provides descriptions for pageId, target, and sessionId, but not for deltaX or deltaY, which are essential for specifying scroll offsets. The description only clarifies the purpose of target ('bringing a target into view') and adds no meaning to the delta parameters, leaving 40% of the schema undocumented at both levels.

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 and optionally brings a target into view, using a specific verb and resource. It distinguishes itself from sibling tools like browser_click or browser_navigate by focusing on scrolling.

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 provides no explicit guidance on when to use scrolling versus alternatives such as browser_key_down, browser_drag, or browser_resize. It lacks any mention of when to use deltaX/deltaY versus target, and offers no exclusions or alternative references.

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