scroll

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

No annotations are present, so the description carries the full burden. It discloses a key behavioral trait: the tool returns an error if the frontmost application is not in the allowlist. However, it does not detail other behaviors like whether the mouse moves to the coordinate first, or if scrolling is instant or animated.

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 sentences, no fluff. The first sentence states the action, the second adds a crucial precondition. Every word is informative.

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?

For a simple scroll tool with a well-defined input schema, the description covers the essential behavioral constraint (allowlist). A return value or effect statement is missing, but the schema and context make the tool's purpose clear. Some agents might benefit from knowing if coordinates are validated.

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 100%, so the baseline is 3. The description adds no additional meaning beyond the schema's parameter descriptions (coordinate, scroll_direction, scroll_amount). It does not explain values or usage nuances.

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 at the given coordinates,' which is a specific verb ('Scroll') and resource ('coordinates'). It clearly distinguishes from sibling tools like mouse_move (moves cursor) and various click tools, as no other sibling focuses on scrolling.

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 only mentions a condition (frontmost app must be in allowlist) but provides no guidance on when to use this tool versus alternatives, when not to use it, or prerequisites other than the allowlist. No explicit when-to-use or exclusion criteria.

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