scroll

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

Lacks transparency on animation style (smooth/instant), boundary behavior (silent stop at edges), and compatibility with overflow elements. With no annotations, the description should provide more behavioral detail.

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?

Single sentence conveying essential action. No wasted words, front-loaded with the core function.

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?

Provides adequate information for a simple scrolling action, but omits return value and edge cases. With no output schema, brief behavioral notes would improve completeness.

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 coverage is 100%, so baseline is 3. Description adds no new semantics beyond restating parameters. Default value for 'amount' is only present in the schema, not reinforced in the description.

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 verb 'Scroll', the resource 'page', and the means (direction and amount of pixels). It implicitly differentiates from the sibling 'scroll_to_element' which targets an HTML element, not pixel increments.

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 explicit guidance on when to use this tool versus alternatives like 'scroll_to_element'. The usage is implied (pixel-based scrolling) but not clarified with exclusions or preferred contexts.

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