page_scroll

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

No annotations are provided, so the description carries the full burden. It discloses that 'pixels is ignored for top/bottom' which is helpful, but does not mention other behavioral aspects such as whether the scroll is smooth, if it can fail on certain pages, or if it's a non-destructive action.

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 concise with two sentences plus a list. It is front-loaded with the core action. Minor improvement could be integrating the list more naturally, but overall it's efficient.

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 has low complexity and an output schema (not shown). The description covers the core scrolling semantics but omits explanation of the tab_id parameter and potential return values, leaving it somewhat incomplete for a fully autonomous agent.

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?

With 0% schema coverage, the description adds meaning to the direction parameter by listing valid values, and explains pixel behavior for top/bottom. However, it does not explain the tab_id parameter or provide enum constraints, leaving a partial gap.

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 'Scroll the page in a direction.' and lists specific direction values, making the purpose unambiguous. It distinguishes from sibling tools like page_navigate and page_refresh by focusing on scrolling within the current page.

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 usage for scrolling but does not explicitly state when to use this tool versus alternatives (e.g., keyboard scrolling or other navigation tools). No when-not or context cues are provided.

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