nex_browser_drag

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

With no annotations and no additional behavioral details, the description does not disclose what 'drag' entails (e.g., simulated mouse events, prerequisites, side effects). The agent is left without information about the operation's mechanics or 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 a single, focused sentence with no redundant words. It is highly concise and front-loaded with the action and key targets.

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 absence of annotations, no output schema, and the simplicity of the description, the tool lacks essential context such as how drag interacts with the page, what trigger conditions exist, or what the return value might be. The description is too sparse for a real-world browser drag operation.

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 clear descriptions, providing 100% coverage. The tool description adds no extra semantic meaning beyond what the schema already states, so the baseline of 3 is appropriate.

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 action ('Drag') and the resources ('one snapshot ref or selector to another'), making the core purpose obvious. It distinguishes from click/hover/type tools, though it doesn't clarify its relationship with the sibling 'nex_browser_drop'.

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 like nex_browser_drop or other interaction tools. The description only states what it does, not the contexts in which it should be chosen.

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