scroll

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

No annotations provided, so the description carries full burden. It mentions returning a fresh snapshot but fails to disclose scrolling behavior (e.g., scroll amount, infinite scroll handling, side effects). For a mutation tool, this is insufficient.

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 sentence that front-loads the action and includes direction options. Every word is informative with no redundancy.

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?

The tool is simple and has an output schema, so full return value documentation is not needed. However, lacks information on scrolling mechanics (e.g., scroll amount) and when to prefer over 'snapshot'. Adequate but has gaps.

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 has zero description coverage and no enums, but the description adds the two valid values ('down' or 'up'). This provides necessary semantic context beyond the schema, but lacks detail on case sensitivity or behavior.

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 tool's action (scroll the page) and the resource (page), and specifies the two direction options (down/up). It distinguishes from siblings like 'snapshot' by explicitly including the scroll action.

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 implies use for scrolling and getting a fresh snapshot, but does not explicitly state when to use this tool versus alternatives like 'snapshot' or 'click' for navigation. No when-not-to-use or prerequisites are mentioned.

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