app_drag

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

No annotations are provided, so the description carries full burden. It does not disclose potential side effects, error behavior, waiting, scrolling, or other behavioral traits beyond the basic action. Some transparency is present regarding the two modes, but significant gaps remain.

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: first states purpose and use cases, second specifies the required input alternatives. No wasted words, front-loaded, and efficient.

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 the complexity (5 params, two modes), the description provides a high-level overview but lacks details on how source element is specified (ambiguity between top-level `text`/`selector` and `to` sub-object). No return value info. Could be more complete for a moderate-complexity 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 description coverage is 100%, so baseline is 3. The description adds value by clarifying the logical alternative between `to` and `offset` and by providing examples of use cases, which enhances understanding 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 the action (drag), the methods (by selector/text or offset), and concrete use cases (sliders, range inputs, reordering lists, canvas handles). It effectively distinguishes from sibling tools like app_click and app_scroll.

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 explains that you provide either `to` or `offset`, giving two modes, but does not specify when to choose one over the other, nor does it provide when-not-to-use or compare with siblings.

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