browser_drag

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

The description lacks behavioral details beyond the basic action. It does not disclose whether events are fired, if there are side effects, or if actions are reversible. With no annotations provided, the description carries full burden but fails to inform about potential failures or safety.

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 concise, using a docstring format with Args and Returns sections. It is front-loaded with the action statement. Only essential information is included, though it could be slightly more compact.

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 no annotations, no output schema details, and 4 parameters with 0% schema coverage, the description is incomplete. It does not mention error handling, behavior when elements are not found, or what constitutes a successful drag. The return value is only 'Success message' without specifics.

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 has 0% description coverage, leaving all parameters undocumented. The description adds some meaning by labeling start_element as 'Human-readable source element description' and start_ref as 'Exact source element reference from the page snapshot,' which helps distinguish the two. However, it still lacks format or example values.

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?

Description explicitly states 'Perform drag and drop between two elements.' The verb 'drag and drop' is specific to this action, and the resource 'elements' is clear. This distinguishes it from sibling tools like browser_click or browser_hover, which are single-element actions.

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 browser_click or browser_type. There is no mention of prerequisites (e.g., needing a page snapshot to obtain element references) or scenarios where drag and drop is appropriate.

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