Drag mouse

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

Annotations indicate readOnlyHint=false (mutating) and destructiveHint=false (not destructive), which aligns with a drag-and-drop action. However, the description does not mention side effects like triggering events or moving elements, though this is not critical for such a common operation.

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 a single, concise sentence that contains all necessary information without fluff. It is well-structured and easy to parse.

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 low complexity of the tool, the description is complete enough for an agent to invoke it correctly. No output schema is present, but a drag-and-drop action typically returns a status or nothing, and the description does not need to detail that. Minor gap: no mention of success/failure behavior, but not essential.

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% (both startTarget and endTarget are described). The parameter descriptions 'Source element ref or CSS selector' and 'Target element ref or CSS selector' are clear and self-explanatory. The tool description adds no additional meaning 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?

The description clearly states the action: 'Drag and drop from one element to another.' It is specific and distinguishes itself from element-based actions like click and hover, and from coordinate-based drag (mouse_drag_xy) and drop actions.

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 explicitly mention when to use this tool over alternatives such as mouse_drag_xy or drop. It is implied that this is for element-based drag-and-drop, but no explicit guidance is provided.

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