ui_drag

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

Discloses key behaviors beyond the minimal annotation (openWorldHint: false): rejects identical coordinates, enforces minimum speed_ms of 20 ms for reliable drag thresholds, and describes optional modifier support. No contradictions.

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 clear sections (modes, args, notes). No redundant or irrelevant information. Each sentence adds value.

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 8 parameters, no output schema, and extensive sibling tools, the description is complete: covers prerequisites, edge cases (identical coordinates, short drags), and alternatives. An agent can use this tool correctly without additional 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%, so the description must explain all parameters. It does so comprehensively: defines each coordinate and automation ID, explains speed_ms minimum and purpose, and lists accepted modifier values. Adds essential context beyond the schema.

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 'Drag from one position to another' and defines two distinct modes (By AutomationId and By coordinates). It differentiates from sibling tools like ui_click by specifying when to use that alternative (short drags).

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?

Provides explicit usage guidance: when to use each mode, prerequisite for mode 1 (call ui_get_window_tree first), and conditions to use ui_click instead. This helps the agent choose correctly.

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