scroll

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

With no annotations, the description carries the full burden, and it does disclose one genuine behavioral trait: it is a real wheel gesture with momentum rather than an instant jump. That is meaningful for automation timing. It stops short of stating what gets scrolled, direction, amount, or any permission/session requirements.

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 short sentence with no filler, and the distinguishing trait (momentum vs jump) is front-loaded. It is arguably under-specified rather than over-long, which is not a conciseness failure.

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 zero-parameter tool with no output schema, the description is minimally adequate but leaves open what is being scrolled (page vs. element) and how far. In a browser-automation sibling set, that ambiguity is worth resolving, though the tool's simplicity limits the damage.

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 tool takes zero parameters, so the baseline of 4 applies. There is nothing for the description to clarify or compensate for, and the schema (empty object) is sufficient.

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 name 'scroll' plus the phrase 'a real wheel gesture with momentum' conveys the action and its manner, so an agent can infer the purpose. However there is no explicit verb+resource statement (e.g. 'scrolls the page viewport') and no differentiation from siblings like navigate, open_page, or interact, which all move within a page context.

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 when-to-use guidance, no conditions, and no alternatives. It never says to use this instead of, say, navigate or interact, nor when a momentum scroll is preferable. Usage is entirely left to inference.

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