browser_scroll

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

Annotations already declare openWorldHint=true and destructiveHint=false, but the description adds no additional context such as whether the scroll completes synchronously, whether it triggers lazy loading, or how it interacts with the viewport state. The one sentence merely restates the schema.

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 with no wasted words, though the phrase 'in a given direction' is mildly redundant with the direction parameter already in the schema.

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 simple scroll action with full schema coverage, the definition is minimally viable, but it omits any note about whether scrolling is instant or animated, whether lazy content is triggered, or what the call returns (no output schema exists). An agent can call it, but not fully predict the effect.

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 description coverage is 100% – direction's enum, the distance default of 500 pixels, and session_id's provenance are all documented in the schema. The description adds nothing beyond that, so the baseline 3 applies.

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 names a specific verb (scroll) and resource (the page) and the direction parameter, so an agent knows exactly what the tool does. It does not, however, distinguish itself from adjacent viewport tools such as browser_press_key or browser_evaluate, which can also move the page.

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?

There is no when-to-use guidance: nothing says to call this before a screenshot, when content is below the fold, or that browser_wait may be needed for lazy-loaded content. No alternatives or exclusions are mentioned.

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