browser_scroll

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

No annotations present, so description must carry the burden. It does not disclose defaults (down 400px from schema), nor does it explain behavior differences between direction values like 'top' vs 'down'. No mention of whether scrolling is smooth or instant.

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 with no filler. It is front-loaded and efficiently communicates the core action.

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?

Given no output schema and no annotations, the description should cover how to scroll an element (since it mentions 'element' but provides no parameter to specify one). This omission leaves the tool underspecified for practical use.

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 provides full coverage for both parameters (direction enum, amount number with defaults). Description adds no extra semantic meaning beyond the schema, so baseline score of 3 is appropriate.

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 action ('Scroll') and targets ('the page or an element'), distinguishing it from sibling tools like 'browser_click' or 'browser_navigate'. However, it is overly generic and doesn't specify that scrolling is typically for viewport navigation.

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?

No guidance on when to use this tool vs alternatives. No mention of prerequisites (e.g., page must be loaded) or exclusions (e.g., not for scrolling specific elements unless selected earlier).

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