drag_by_uid_to_uid

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

The description mentions 'HTML5 drag events' which provides some insight into the behavior, but it does not disclose the specific events dispatched, whether it waits for drop, or any side effects. The annotation readOnlyHint=false already indicates mutation, but the description adds minimal additional behavioral context.

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 sentence of six words, containing no fluff. It efficiently conveys the core action and the event type. Every word is purposeful.

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 simple drag tool with two parameters and no output schema, the description is adequate but not exhaustive. It could mention the outcome (e.g., source element is dragged to target) or error conditions (e.g., element not found, not draggable). Nonetheless, the schema and name fill in some gaps.

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?

The input schema already provides full descriptions for both parameters (source UID and target UID). The description adds no further semantic value beyond implying the direction of drag. Baseline of 3 is appropriate given 100% schema coverage.

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 it performs a drag action using HTML5 drag events, distinguishing it from sibling tools like click_by_uid or hover_by_uid. However, it could be more explicit about source and target elements, though the parameter names clarify this.

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?

No guidance on when to use this tool vs alternatives or when not to use it. It simply describes the action without providing context such as prerequisites (e.g., elements must be draggable) or alternatives (e.g., using keyboard or mouse events).

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