browser.drag_drop

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

No annotations are provided, and the description lacks behavioral details such as whether the tool waits for the drag to complete, triggers events, or requires specific permissions. It only states the action without side effects or constraints.

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 extremely concise with two short sentences. The first sentence immediately conveys the purpose, and the second provides essential parameter usage. No wasted words.

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 complexity of drag-drop operations (multiparameter, coordinate vs selector), the description covers the input logic but lacks behavioral details and explanation of the session_id parameter. It is adequate for basic use but not fully comprehensive.

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 description adds significant value beyond the input schema by explaining the OR relationship between source_selector and (source_x, source_y), and similarly for target. This is critical understanding that the schema alone (with 0% description coverage) does not convey. However, it does not explain the required session_id parameter.

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 tool's action ('Drag from one element or coordinate to another'), which is a specific verb and resource. It distinguishes itself from siblings like browser.execute_action or browser.find_elements by explicitly naming the drag operation.

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?

The description provides usage guidance on how to specify source and target (using selectors or coordinates), which is helpful. However, it does not mention when to use this tool versus alternatives, nor does it include any prerequisites or exclusions.

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