scroll

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

No annotations are present, so the description carries full burden. It discloses that scrolling occurs in the frontmost application but omits potential behaviors such as whether it waits for scroll to complete, fails on non-responsive apps, or has rate limits. The mention of preferring batch_actions is behavioral but limited.

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 extremely concise, consisting of two sentences with no redundant words. The first sentence states purpose, and the second provides critical usage guidance. Every sentence earns its place.

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's low complexity (2 simple params, no output schema), the description covers the essential purpose and usage guidance. It could be improved by mentioning potential limitations or expected behavior when the frontmost app is not scrollable, but overall it is reasonably complete.

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 coverage is 100%, and the description adds value by clarifying that parameters apply to the frontmost application, which is not in the schema. This extra context helps the agent understand the scope of the direction and amount. However, it does not elaborate on the default amount or valid ranges 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?

The description clearly states the verb 'Scroll' and identifies the resource 'the frontmost application'. It distinguishes itself from sibling tools like click_at or type_text, and explicitly references batch_actions for when combining actions.

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 explicit guidance to prefer batch_actions when combining with other actions, helping avoid redundant tool calls. However, it does not specify when not to use scroll or mention any prerequisites or alternative scrolling methods.

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