browser_drag

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

No annotations are provided, so the description carries the full disclosure burden. It usefully identifies synthetic HTML5 drag events but omits crucial behavior: side effects, whether it waits for drop handlers, error behavior on missing selectors, and whether the drag is trusted. This is below minimum viable for an unannotated interaction tool.

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 sentence, front-loaded with the core action and resource, with no wasted wording. It is appropriately sized for the core purpose even though additional detail is needed elsewhere.

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 browser interaction tool with no annotations and no output schema, the definition is too thin. It lacks parameter usage, behavioral caveats, and routing guidance among the many sibling browser tools, leaving an agent under-informed.

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 0%, so the description must compensate. 'From one element to another' loosely maps to from_selector and to_selector, but tab_id is never mentioned and no selector syntax or constraints are given. Partial compensation leaves a significant gap.

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?

States a specific verb (drag-and-drop) and resource (one element to another) and specifies the mechanism (synthetic HTML5 drag events). It does not explicitly differentiate itself from sibling interaction tools such as browser_click or browser_trusted_click, but the 'synthetic' qualifier is meaningful.

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?

Provides no when-to-use guidance, no alternatives, and no exclusions. An agent cannot tell from the description whether to prefer this over browser_click, browser_hover, or any trusted-event variant, nor when drag-and-drop is inappropriate.

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