Scroll Up

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does explain the intended effect, but it is silent on how the amount parameter influences the scroll, how device and som_id determine the target context, and what observable side effects or limits exist. For a UI action with three parameters, this is thin.

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, and the parenthetical adds meaningful clarification rather than redundancy. However, it is so terse that it leaves all parameter-level information unaddressed, so it is not fully appropriately sized for the tool's complexity.

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?

Although an output schema exists, the definition is not complete enough for correct invocation: parameter semantics are undocumented and there is no guidance for choosing among the many sibling navigation tools. Scroll direction alone is insufficient for reliable use.

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%, and the description never mentions amount, device, or som_id. An agent cannot determine whether amount is a fraction of the viewport, a pixel distance, or a scroll unit, nor what device and som_id refer to. The description adds no value over the raw parameter names.

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 a specific verb ('scroll'), a resource ('content'), and a direction ('up'), with the parenthetical clarifying that this reveals content above the current viewport. This clearly separates it from scroll_down, scroll_left, and scroll_right by direction, though it does not explicitly contrast it with scroll_to or swipe.

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 this tool versus alternatives such as swipe, scroll_to, or other scroll directions. The phrase 'reveal what is above' weakly implies a use case, but no explicit conditions, exclusions, or alternative routing are provided.

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