browser_drag

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

Annotations already signal that the tool is destructive (destructiveHint=true) and not read-only, so the safety profile is covered. The description adds that this is a two-element gesture, but it stops short of explaining what happens on drop or what side effects to expect.

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?

A single, direct sentence states the action and the objects involved with no wasted words. The key information is front-loaded.

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 small tool with full schema coverage and annotations, the description is functional. It lacks any note on permissions, visibility requirements, or expected behavior after the drop, but the structured data covers most invocation details.

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?

Input schema covers 100% of parameters with meaningful descriptions (startTarget/endTarget, startElement/endElement). The description adds only the 'between two elements' relationship, which is helpful but not necessary given 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?

Description uses a specific verb ('Perform drag and drop') and names the resources ('between two elements'), making the core action clear. It does not explicitly distinguish browser_drag from the similarly named sibling browser_drop, so it is clear but not differentiated.

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 given on when to choose this tool rather than siblings like browser_click, browser_hover, or especially browser_drop. There are no stated prerequisites, caveats, or alternative conditions.

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