browser_drag

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

Annotations already indicate destructiveHint=true and openWorldHint=true, but the description does not elaborate on specific behaviors, such as how drag events are simulated, whether it requires WebDriver or Playwright, or what happens if elements are not draggable. It adds minimal value beyond the annotations.

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 with zero wasted words. It conveys the essential action efficiently.

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 has 4 parameters and no output schema, but the description omits details about return values, error cases, or how the drag-and-drop coordinates are interpreted (e.g., center points vs. specific locations). It fails to fully inform an agent about the tool's capabilities and limitations.

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 covers all 4 parameters with full description coverage (100%). The tool description does not add any additional meaning to the parameters beyond what the schema already provides, such as clarifying the difference between startElement and startTarget. Baseline of 3 is appropriate given high 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 uses a specific verb ('Perform drag and drop') and clearly identifies the resource ('between two elements'). It effectively distinguishes this tool from sibling tools like browser_click, browser_hover, and browser_drop (which might only handle the release phase).

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, such as browser_drop for only releasing, or what prerequisites are needed (e.g., obtaining element references via snapshot). The description lacks any contextual hints about ideal scenarios or exclusions.

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