adb_input_drag

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

No annotations provided. Description states it uses Android's draganddrop input command and simulates a drag gesture, but does not disclose side effects, permissions, or system behavior beyond the action.

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 concise sentences: first states action, second adds context (use cases, underlying command). No unnecessary words.

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?

Covers purpose and use cases but lacks information about return values, failure modes, or prerequisites (e.g., display on, no blocking UI). Without output schema, more context on outcome would be helpful.

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 100% with descriptions for all parameters. The tool description adds no new semantic information 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?

Clear verb ('Drag') and resource ('point to another on screen'). Distinguishes itself from sibling input tools (fling, pinch, tap, etc.) by specifying drag-and-drop, sliders, map panning, reorder use cases.

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?

Mentions uses (drag-and-drop, sliders, etc.) but lacks explicit when-not-to-use or comparison to alternatives like adb_input_fling or adb_input_pinch.

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