scroll

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

The description mentions 'via swipe gesture' which suggests simulation of a user gesture, but it lacks details on the behavior: e.g., whether it simulates a full swipe or a partial swipe, whether it works on all platforms, or what happens if the content cannot be scrolled. No annotations exist to fill this gap.

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 very short (one sentence), which is concise but at the expense of completeness. It does front-load the core purpose but omits important details. It is well-structured for a brief definition but could include more information without being verbose.

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 4 parameters, no output schema, and no annotations, the description is severely incomplete. It does not cover return values, preconditions, side effects, or parameter semantics. The tool is part of a UI automation context, and the description lacks context needed for correct invocation.

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 does not explain any of the four parameters beyond what is obvious from the schema (e.g., direction is self-explanatory). The meanings of 'sessionId', 'distanceRatio', and 'durationMs' are not clarified. With 0% schema description coverage, the description should have compensated but did not.

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 tool's purpose: to scroll screen content via a swipe gesture. It specifies that it does so in a direction, which aligns with the 'direction' parameter. While it doesn't explicitly distinguish from siblings, the verb 'scroll' is unique among the listed siblings, so the purpose is sufficiently clear.

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 guidance is provided on when to use this tool instead of others, or when it should not be used. There is no mention of prerequisites, contexts where scrolling might fail (e.g., no scrollable content), or comparison with alternatives like tapping or pressing back.

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