scroll

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

Without annotations, the description explains the direction of scrolling (positive/negative) and hints at observe/settle_ms behavior by referencing click(). However, it does not disclose whether scrolling is smooth, affects all instances, or has any side effects.

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?

Two short sentences that front-load the essential meaning. No superfluous text; each word serves a purpose.

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 no output schema and rich sibling tools, the description lacks details on return values, interaction with other tools, and precise behavior. It is insufficient for an agent to use confidently.

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 description coverage and 4 parameters, the description only partly explains 'amount' (direction) and references observe/settle_ms. It does not explain 'instance' or the units of 'amount' (pixels/lines), leaving significant gaps.

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 states 'Scroll: positive = up, negative = down', clearly indicating the action and direction semantics. It distinguishes from siblings like 'drag' by focusing on scrolling behavior.

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 explicit guidance on when to use scroll instead of alternatives like drag or click. The reference to click() for observe/settle_ms is minimal and does not provide context for choosing this tool.

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