scroll_page

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

No annotations are provided, so the description must carry the full burden. It adds only the phrase 'native one-page scroll,' which hints at the scrolling mechanism but does not disclose edge-case behavior (e.g., what happens if the page is not scrollable), whether the scroll waits for completion, or any side effects. The behavior beyond the core action is largely unspecified.

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?

The description is a single, front-loaded sentence that immediately conveys the tool's core function. There is no filler or redundant information, making it optimally concise and well-structured.

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 return values are covered. However, the description omits usage guidance relative to sibling tools and leaves the 'session_id' parameter undocumented in both schema and description. For a straightforward scroll gesture, the description is adequate but not fully complete.

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?

The schema already describes the 'direction' and 'device' parameters with meaningful context (e.g., content direction vs. finger swipe direction). The description adds the concept of 'exactly one viewport page,' which helps interpret the effect of 'direction.' However, it does not clarify the 'session_id' parameter, and the description alone adds minimal parameter-level detail.

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 action: 'Scroll exactly one viewport page' with the qualifier 'native one-page scroll.' This distinguishes it from siblings like swipe (which can be arbitrary) and scroll_until (which scrolls until a condition), making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as swipe, scroll_until, or smart_scroll. It does not mention preconditions, exclusions, or scenarios where this tool is preferred, leaving the agent to guess based on the name and behavior.

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