scroll

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

Discloses side effects (modifies DOM scroll position, observable but reversible), prerequisites (active Chrome tab with content), and return value (confirmation). No annotations provided, so description carries full burden; it is sufficient but not exhaustive.

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?

Extremely concise: three sentences covering purpose, side effects, prerequisites, and return. No wasted words; front-loaded with key action.

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?

Completely covers the tool's functionality given no output schema: explains all parameter interactions, prerequisites, return value, and side effects. Handles complexity of 4 parameters well.

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. The description adds value by explaining interactions between parameters (e.g., selector overrides others) and defaults, beyond schema descriptions.

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 scrolls the page by pixel offset, viewport pages, or to a specific element via CSS selector. It distinguishes from sibling tools like 'click_element' and 'evaluate_js'.

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?

Explicitly says 'Use this to navigate within long pages or bring elements into view' and provides alternatives: 'click_element' and 'evaluate_js' for different scroll scenarios.

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