scroll

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

The description adds no behavioral context beyond what the name and schema imply. It does not explain units, sign conventions, whether the scroll is relative, or any side effects. The destructiveHint annotation is present but not elaborated, and scrolling is not inherently destructive.

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 with no filler. It is concise and easy to parse, though the brevity leaves important behavioral details unstated.

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?

For a tool with no output schema and only a destructiveHint annotation, the description is too sparse. An agent cannot determine what dx/dy mean operationally, how scrolling behaves at boundaries, or what side effects to expect.

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?

Schema description coverage is 0%, so the description must compensate. It identifies dx/dy as scroll deltas and uid as the element identifier, but it does not specify units, direction semantics, or whether values are relative/absolute.

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 uses a specific verb ('Scroll') and a precise resource ('the element identified by uid'), and it names the operation's inputs (dx/dy). It is clearly distinguishable from sibling tools like click, type, and navigate.

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 clearly implies when to use it: when you need to scroll an element by a delta. It does not explicitly mention alternatives or exclusions, but the context is sufficiently clear for a simple scroll operation.

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