scroll

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

With no annotations provided, the description carries the behavioral disclosure burden. It usefully reveals the 90-second timeout, the caller-supplied budget extension, and the fact that app scroll physics determine the final offset. It does not mention side effects like triggering navigation or lazy loading, but the core execution expectations are well covered.

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 two sentences with no filler. It front-loads the core purpose, then adds amount semantics and timeout behavior in a compact, scannable way.

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 high schema coverage and presence of an output schema, this is a reasonably complete description for a 23-parameter interaction tool. The main gaps are the lack of sibling differentiation and the vague reference to a 'caller-supplied budget' that is not visible in the parameter schema, but neither prevents an agent from using the tool correctly in most cases.

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 schema covers 96% of parameters, so the baseline is 3. The description adds meaningful semantic value for the key 'amount' parameter by defining it as a finger-path fraction of the viewport axis, and clarifies that top/bottom target edges of the scrollable content. This goes beyond the generic schema text.

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 names a specific action ('Scroll'), a clear resource ('scrollable content'), and the direction/edge semantics via the direction enum values. However, it does not explicitly differentiate this tool from closely related siblings like swipe or gesture, so it stops short of a 5.

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?

There is no guidance on when to use scroll versus alternatives such as swipe or gesture, and no exclusion conditions are stated. The amount semantics are explained, but that is a how-to detail rather than usage routing.

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