desktop_scroll

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

Description provides no behavioral details beyond the action. No mention of scroll speed, direction, amount limitations, or edge behavior. With no annotations, agent has no safety cues.

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?

Extremely concise (3 words) but at the cost of completeness. Structure is missing; no separation of purpose, usage, or parameters.

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?

With 5 parameters and no output schema, the description is grossly inadequate. Agent lacks information to correctly invoke the tool.

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 0%. Description only hints at x,y coordinates but fails to explain 'amount', 'direction', or 'id' parameters. Agent cannot infer parameter meanings from this description.

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 'Scroll at (x,y)' clearly identifies the action (scroll) and basic resource (coordinates), but lacks specificity about what is being scrolled (e.g., screen vs. active window), which reduces clarity.

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 on when to use this tool vs. siblings like desktop_click or desktop_drag. Missing context for prerequisites or alternatives.

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