browser_drag

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

There are no annotations, so the description carries the full burden of behavioral disclosure. 'Drag from one element to another' implies an interaction, but it does not describe side effects, whether events are triggered, whether the action is reversible, or what the tool returns. This is comparable to a mutation tool that states its action without explaining consequences.

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 very concise and front-loaded, with no filler. Both clauses earn their place by stating the action and the accepted input modes. It is efficient, though slightly underspecified.

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 tool with no annotations, no output schema, and four undocumented optional parameters, this description is not complete. An agent would need to infer prerequisites such as needing a snapshot first, the effect of the drag, and what happens on success or failure.

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, the description must compensate. 'Accepts snapshot refs or selectors' adds useful meaning by explaining the two addressing modes, but it does not map these to fromRef/toRef and fromSelector/toSelector, clarify whether the modes are exclusive, or describe how the from/to pairs relate.

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 ('Drag') and resource ('from one element to another'), which clearly identifies the tool's core action and distinguishes it from siblings like browser_click and browser_hover. However, it does not explicitly differentiate itself from alternatives or state what makes it unique beyond the drag action.

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 about when to use this tool versus browser_click, browser_hover, or browser_select. The description mentions that it accepts snapshot refs or selectors, but does not explain when one addressing mode is preferred or whether both are required.

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