Drag and drop

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses a key limitation: some JS libraries need intermediate mousemove events that this tool does not emit. It also warns about silent failures and suggests a workaround. This is valuable behavioral context not inferable from annotations.

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 concise yet rich: three short paragraphs cover the action, a prerequisite, and a behavioral caveat with a workaround. Every sentence serves a distinct purpose; 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?

For a complicated interaction tool like drag-and-drop, the description is complete: it covers prerequisites, supported scenarios, limitations, and alternatives. The input schema and output schema handle parameter details and return values, leaving the description to add critical operational context.

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%, so the baseline is 3. The description adds slight semantic value by clarifying that 'both uids must come from the same take_snapshot,' emphasizing a constraint not made explicit in the schema (which only says 'from the most recent take_snapshot' for each). This helps disambiguate the relationship between from_uid and to_uid.

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 action: 'Drag one element onto another (press, move, release).' This verb+resource phrasing distinguishes it from sibling tools like click, hover, and click_at.

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?

It explicitly explains when to use the tool (for native HTML5 drag-and-drop and mouse-driven sortable lists) and provides an alternative when it fails: 'drive it manually with click_at and press_key instead.' It also notes the prerequisite that both uids come from the same take_snapshot.

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