Drag and drop

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

Annotations declare readOnlyHint=true, but the description describes an interactive drag gesture that inherently changes UI state, creating a direct contradiction. No additional behavioral context is provided beyond the percentage tip.

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 the core action and a useful tip. No filler or redundancy.

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?

Despite the schema covering parameters, the tool lacks an output schema and the description does not explain return values, failure modes, or side effects. The annotation contradiction further weakens trust. For a 10-parameter interaction tool, this is insufficiently 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?

All 10 parameters have schema descriptions with 100% coverage, so the baseline is 3. The description adds practical value by explaining that percentage coordinates (0-1) are safer for positions estimated from screenshots, going beyond the raw schema definitions.

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 uses a specific verb ('Drag') and resource ('an element') and states the action is from one point to another, clearly distinguishing it from sibling tools like tap or swipe by naming the input type 'draganddrop'.

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 provides no explicit when-to-use or when-not-to-use guidance relative to sibling tools such as swipe. It only implies usage by describing the drag action itself and gives a tip about using percentages for screenshots, which is a parameter-level hint rather than tool-selection guidance.

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