scroll

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

No annotations are provided, so the description carries the behavioral disclosure burden. It reveals the core action and the infinite-scroll usage pattern, but does not explain what happens if a selector is invalid, whether scrolling is instant or animated, or whether any output is returned.

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 verb and target, then adds a genuinely useful parenthetical hint about infinite scroll. No filler or repetition.

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 core purpose is clear and sufficient for a trivial scroll call, but with no output schema, no annotations, and little parameter guidance, the description alone does not fully equip an agent for edge cases or exact behavior. It is adequate but has notable 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 descriptions are completely absent (0% coverage), so the description needs to compensate. It hints at 'element' for selector and 'down' for direction, but does not explain the amount parameter, the direction enum values beyond down, or how selector interacts with the page. The compensation is partial at best.

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 ('scroll') and identifies the targets clearly: the page or an element. Among the sibling tools, none other offers scrolling, so this tool is immediately distinguishable.

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 when to use the tool and adds a practical note about repeating down-scrolls for infinite scroll. It does not explicitly name alternatives or exclusions, but no sibling provides the same capability, so the context is clear enough.

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