browser_scroll

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

Describes behavioral traits: pixel scrolling with direction/amount, element scrolling via ref, default values, returns a snapshot. No annotations provided, so description carries full burden and does well, though could mention non-destructive nature.

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?

Very concise: two sentences plus a bullet-like format. Front-loaded with the main action. Every sentence adds value without 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?

Covers main functionality and usage context. Output schema exists for return values. Minor gap on session_id parameter, but overall complete for the tool's 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?

Adds meaning to direction and amount (pixels, defaults) and ref (scrolls element into view, ignoring direction/amount). Session_id is not explained, but schema coverage is 0% so description compensates well for main parameters.

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?

Description clearly states it scrolls the page by pixels or scrolls an element into view, using specific verbs and resources. It distinguishes between two modes and from sibling tools like browser_scroll_to_bottom implicitly.

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?

Explicitly says to use it for triggering lazy-loaded content or revealing off-screen elements, providing good context. Does not compare to sibling browser_scroll_to_bottom, but the use case is clear.

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