drag_by_uid_to_uid

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

Annotations indicate readOnlyHint=false, which aligns with the drag action. The description adds context about using HTML5 drag events, but does not disclose potential side effects, error conditions, or requirements beyond the schema fields.

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 with no extraneous information. It is front-loaded and directly states the action and mechanism.

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, the description covers the essential purpose and parameters. However, it lacks context about prerequisites (e.g., elements must be on same page), error handling, or behavior when drag fails, which would be helpful given the complexity of drag events.

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% with clear descriptions for both parameters. The description does not add meaning beyond the schema, as 'drag element to another' already implies the from and to UIDs are needed.

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 target (another element), with a specific verb-resource pair. It distinguishes from sibling tools like click_by_uid and hover_by_uid by specifying HTML5 drag events.

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 implies usage for drag-and-drop interactions, but provides no explicit guidance on when to use this tool versus alternatives like keyboard events or script evaluation. No exclusion criteria or prerequisites are mentioned.

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