scroll

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

With no annotations, the description carries the burden of explaining behavior. It discloses that scrolling occurs in the current tab and that a new snapshot is returned, but it does not mention scroll increments, end-of-page behavior, or handling of lazy-loaded content. This is adequate but not richly transparent.

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, front-loaded sentence with no filler. Every word contributes to stating the action and the return value.

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 tool with one optional parameter and no output schema, the description covers the core action and result. It omits edge cases and boundary behavior, but the low complexity means this is unlikely to block correct invocation.

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 only parameter, direction, is referenced in the description ('down (or up)') with values matching the schema enum. However, with 0% schema description coverage, the description adds little beyond restating the enum and does not explain default behavior or scrolling amount.

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 uses a specific verb and resource ('Scroll the current tab down (or up)') and states the returned result ('return the new snapshot'). It is distinguishable from siblings like click, type_text, and browse, though it does not explicitly contrast itself with the related snapshot tool.

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 is provided about when to use scroll versus browse, snapshot, or extract. The description only states the action itself, leaving the agent to infer appropriate usage from the tool name and sibling list.

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