drag_drop

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

No annotations are present to declare read-only or destructive behavior, so the description carries the disclosure burden. It does disclose the implementation fallback (swipe on older versions), which is valuable. However, it doesn't mention whether the input draganddrop interface requires a debug shell or if there are side effects like triggering long-press behavior.

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, compact and front-loaded with the core purpose. It adds the platform-specific implementation detail efficiently without waste.

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?

The tool has a well-documented schema (100% coverage) and an output schema, but the description is minimal for a gesture tool with a platform fallback. Given the sibling 'swipe' tool, more guidance on when drag_drop is preferable and the behavioral caveat of the fallback would improve completeness.

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%, with all parameters documented in the schema. The description adds the duration parameter's meaning implicitly (gesture speed) but doesn't add details beyond what the schema provides. Baseline 3 is appropriate when schema covers all parameters.

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 tool performs a drag and drop gesture between two points, with a specific verb and resource. However, it doesn't explicitly distinguish this from sibling tools like 'swipe' or 'scroll' beyond the implementation detail. The title 'Drag and Drop' reinforces the purpose.

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 mentions the platform version distinction (Android 8.0+ uses input draganddrop, older versions fall back to swipe), which gives some usage context. However, it doesn't explicitly say when to use this vs the 'swipe' sibling tool, nor does it note that on older Android versions the behavior may differ from a true drag-and-drop gesture.

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