nex_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 behavioral burden. It discloses a CAPTCHA-handling rule and a prohibition, but says nothing about drag mechanics, side effects, waiting behavior, permissions, or what happens after the drag.

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 purpose is front-loaded in the first sentence, followed by a concise CAPTCHA directive. Both sentences are relevant and there is no wasted text.

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 description covers the core action and an important CAPTCHA warning, while the schema covers parameter details. However, for a browser interaction tool with no annotations and no output schema, it omits return behavior, failure modes, and drag-specific behavioral context.

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 the schema already documents all four parameters, including startTarget and endTarget as snapshot refs or unique CSS selectors. The description adds no parameter meaning beyond what the schema already provides, making 3 the appropriate baseline.

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: dragging one snapshot ref or CSS selector to another. This is clear enough to identify the operation, though it does not explicitly distinguish itself from the sibling nex_browser_drop tool.

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?

It gives a concrete CAPTCHA-related alternative: start with nex_browser_captcha_prepare and do not use scripted drags for CAPTCHAs. It lacks general guidance on when to use drag versus other interaction tools such as drop or click, but the explicit exclusion is valuable.

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