browser_drag

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

The description adds no behavioral detail beyond the fact that it performs a drag and drop. Annotations already indicate destructiveHint=true, so the agent knows it modifies state, but the description does not explain potential side effects (e.g., triggering events, layout changes) or how the tool interacts with the page.

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 extremely concise (one short sentence), which is good for front-loading, but it lacks important details about element selection and permissions. It earns its place, but more context could be included without becoming verbose.

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?

Given the complexity of drag-and-drop interactions and the presence of four parameters (including startElement/endElement for human-readable descriptions), the description fails to explain how to properly use these parameters or that the tool relies on page snapshot references. No output schema exists, but the description does not clarify return behavior or error conditions. The description is insufficient for an agent to reliably invoke the tool.

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 description coverage is 100%, so all four parameters already have descriptions in the schema. The tool description does not add any additional meaning or constraints to the parameters beyond what the schema provides. Baseline 3 is appropriate as the schema carries the full burden.

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 tool performs a drag and drop between two elements, which is a specific verb-resource combination. Among siblings like browser_drop and browser_click, it distinguishes itself by explicitly naming the drag-and-drop action. However, it doesn't fully disambiguate from browser_drop, which might be related.

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_click, browser_hover, or browser_drop. There is no mention of prerequisites (e.g., needing a page snapshot) or conditions under which drag-and-drop is appropriate or should be avoided.

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