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 adds a small implementation detail, but does not disclose side effects, requirements for the source/target elements, or what behavior occurs after the drag. With readOnlyHint=false, the mutation nature is implied but not elaborated.

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, front-loaded sentence that conveys the core functionality with zero wasted words. Very concise and appropriately sized for the tool's simplicity.

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 is simple with two fully documented parameters, so the description is minimally sufficient. However, it lacks broader context such as usage scenarios, potential side effects, or behavior when the drop target is invalid, making it slightly incomplete.

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 provides 100% coverage with descriptions for both parameters (fromUid and toUid), so the description adds no extra semantic value. Baseline of 3 is appropriate since the schema handles parameter documentation.

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 the target (another element), which is specific enough to distinguish from sibling tools like click, hover, and fill. However, 'to another' is slightly vague without referencing the toUid parameter, but the schema resolves 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 is provided on when to use this tool versus alternatives, nor any prerequisites (e.g., element must be draggable or have a valid drop zone). The description does not mention any exclusions or context.

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