Touchpoint

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

No annotations provided, so description carries full burden. Adds context that this positions for subsequent scroll operations, but omits behavioral details like whether movement triggers hover events, animation smoothness, or coordinate system origin.

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?

Well-structured with purpose front-loaded, followed by usage guidance, then Args documentation. Necessary verbosity given zero schema coverage; no redundant sentences.

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 output schema present, return values need not be explained. Given zero annotations, adequately covers the core interaction pattern but should disclose side effects (hover states) or timing behavior for a complete automation context.

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%, requiring description to compensate. Args section documents all 3 parameters with clear semantics and mutual exclusivity logic ('use with y instead of element_id'), effectively filling the schema documentation gap.

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?

Clear verb 'Move' with specific targets (element or screen coordinates). Explicitly references sibling 'scroll()' to establish tool relationships and positioning purpose.

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?

Explicitly states 'Use this before scroll() to scroll within a specific area,' providing clear sequencing guidance. Lacks explicit 'when not to use' or alternatives (e.g., direct clicking), but provides concrete usage context.

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