drag_drop

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

With no annotations, the description carries full burden. It discloses version-dependent behavior (API 26 vs fallback) but omits other behavioral traits such as prerequisites (e.g., screen state) or effects of the gesture beyond movement. It adds value but is not comprehensive.

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?

The description is two sentences long, front-loads the primary purpose, and includes a critical version-specific detail without any superfluous words. Every sentence earns its place.

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 tool's simplicity (gesture without complex outputs), the description covers the main behavior and version handling. It is reasonably complete for a 6-parameter tool, though it could mention coordinate constraints relative to screen boundaries.

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 each parameter having a basic description (e.g., 'Start X coordinate'). The tool description does not add extra meaning beyond what the schema already provides. Baseline 3 is appropriate.

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 and drop gesture'), the resource ('from one point to another'), and distinguishes from sibling tools like 'swipe' by specifying the use of a dedicated API on Android 8.0+ with a fallback to swipe on older versions. This provides a specific verb and resource context.

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 does not provide explicit guidance on when to use this tool versus alternatives like 'swipe' or 'long_press'. It implies usage for drag-and-drop gestures but lacks clear context, exclusions, or transition cues to other tools.

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