scroll

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

Annotations only include destructiveHint: false. The description adds direction semantics (positive down, negative up) but does not disclose behavior like scroll amount limits, viewport vs element scrolling, or side effects on element references (only implied in snapshot parameter). Minimal beyond annotations.

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?

Single sentence, front-loaded with verb and resource, no waste. Efficient and clear for the information provided.

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 3 parameters and no output schema, the description is incomplete. It omits deltaX, returnSnapshot, and any behavioral details about scrolling beyond direction. An agent would lack critical usage context.

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 description adds value for deltaY by explaining direction, but does not explain deltaX or the returnSnapshot parameter. Schema coverage is low (33%), and the description could compensate more. Baseline 3 due to partial addition.

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') and resource ('current page') and explains the direction based on deltaY sign. However, it omits the horizontal scroll capability via deltaX, which could lead agents to overlook horizontal scrolling. It does not contrast with sibling tools, but siblings are sufficiently different.

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 vs alternatives (e.g., clicking or typing). There is no mention of prerequisites, when not to scroll, or how it compares to other interaction tools.

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