scroll

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

No annotations are provided, so the description carries the full behavioral burden. It discloses a key trait worth knowing: scrolling returns a fresh observation and the observer only surfaces in-viewport elements. However it omits scroll magnitude, direction defaults, behavior at the end of the page, and any focus prerequisite for the 'focused window' case.

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?

Two sentences with no filler. The action and its side effect come first, then the when-to-use condition, so the agent gets purpose before caveat.

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?

An output schema exists, so return-value detail is unnecessary, and the description appropriately references the fresh observation instead. For a zero-required-parameter tool it is nearly complete; it could still say what happens at the page boundary or whether scrolling is incremental.

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% and the parameters are optional with defaults already documented, so the schema does the heavy lifting. The description echoes the 'whole page or focused window' default but adds no syntax or semantics beyond what the schema states.

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?

States a specific verb (scroll), the target (page or focused window), and the post-condition (reveal more content, return a fresh observation). It also implicitly separates itself from the observer by explaining the observer only lists viewport elements, so an agent can route between scroll and observe without opening either schema.

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?

Gives an explicit trigger: use when the element you need is not in the tree yet, because the observer only lists elements inside the viewport. Clear context for adoption, but it names no exclusion and does not explicitly point to a sibling tool (e.g. observe) as the alternative to skip.

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