adb_input_drag

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

No annotations provided, so description carries full burden. It mentions using Android's draganddrop command but does not disclose behavioral details such as whether drag is continuous, intermediate events, lift behavior, permissions, or completion semantics. Insufficient for a mutation tool.

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, front-loaded with action then use cases. No unnecessary words. Highly 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?

Description covers basic purpose and use cases but lacks behavioral details (e.g., coordinate bounds, lift behavior, return value) and does not explain how it differs from similar gestures like fling. Adequate for simple use but not fully complete.

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 has 100% parameter descriptions, so description does not add new meaning. Baseline of 3 is appropriate as schema already documents each parameter adequately.

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?

Description clearly states 'Drag from one point to another on screen' with specific verb and resource, and lists use cases (drag-and-drop, sliders, map panning, reorder). Distinguishes from sibling tools like adb_input_fling or adb_input_pinch.

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 positive use cases ('useful for...'), giving context on when to use the tool. However, lacks negative guidance or explicit comparison to alternatives like fling or scroll, which could improve differentiation.

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