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 burden of behavioral disclosure. It only says 'Drag from one element to another' and does not mention whether this triggers native HTML5 drag events, what side effects occur, how selectors are resolved, or what happens on failure.

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 no filler words. It is concise, though arguably too terse given the tool's complexity and sibling ambiguity.

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 four parameters, no annotations, no output schema, and several closely related sibling tools. The one-line description omits selector semantics, timeout behavior, session requirements, and return values, leaving the agent without enough context to invoke it correctly.

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?

With 0% schema description coverage and no parameter documentation in the description, the agent gets no explanation of sessionId, timeout, or how sourceSelector and targetSelector should be formatted. The phrase 'from one element to another' loosely maps to the two selector parameters, but the description does not compensate for the undocumented parameters.

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 states a specific verb and resource ('Drag from one element to another'), which clearly conveys an element-to-element drag action. It does not explicitly differentiate from the sibling browser_mouse_drag, but the element-to-element framing is distinct enough to establish the basic purpose.

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?

There is no guidance about when to use this tool versus browser_mouse_drag, browser_click, or other interaction tools. The description gives no context about selector-based dragging or when an agent should prefer this over coordinate-based alternatives.

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