scroll_down

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

The description states the tool scrolls the page down to reveal content, which is basic behavior. It does not specify scroll amount, speed, or whether it is safe (non-destructive). Since no annotations exist, the description carries the full burden, and this is minimally adequate.

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 short sentence, which is concise and front-loaded. It could benefit from slightly more detail, but it earns its place without redundancy.

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?

Given the tool has zero parameters and an output schema exists, the description is sufficient to explain the purpose. It is complete for a simple scroll action, though additional context about scrolling behavior would improve it.

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?

There are no parameters, so the schema coverage is 100% by default. The description does not need to add parameter details. A baseline of 4 is appropriate.

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 verb 'scroll' and resource 'page' clearly describe the action. It distinguishes from siblings like 'go_back' and 'navigate' by specifying a scrolling action. However, it doesn't explicitly differentiate from potential other scroll directions or siblings.

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 guidance is provided on when to use this tool versus alternatives like 'click' or 'go_back'. The agent receives no context about typical use cases or scenarios where scrolling is preferred.

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