Scroll Page

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

Provides detailed behavioral traits: small bursts, varied distance, reading pauses, mimicking real users. Highlights reCAPTCHA v3 relevance. Adds significant value beyond the minimal openWorldHint annotation.

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?

Concise with a clear intro, explanatory paragraph, and structured Args list. Every sentence adds value 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?

Covers all aspects: purpose, behavioral nuances, parameter explanations, and return values (direction, amount, humanize). No gaps given the presence of an output schema.

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?

Despite 0% schema coverage, the description fully explains each parameter (direction, amount, humanize, delay_after_ms) with concrete details like 'each ~300px' and 'randomized delay', adding meaning beyond the schema.

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?

Clearly states 'Scroll the active page' with a specific verb and resource. Adds 'human-like increments' to distinguish from basic scrolling, aligning with anti-detection context.

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?

Describes when to use (human-like scrolling to evade behavioral detection) but does not explicitly exclude alternatives like scrolling via JS or other tools. Context is clear but lacks explicit 'when-not-to-use'.

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