element_drag

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

With no annotations, the description carries full burden. It discloses the drag action and parameter modes but does not mention potential side effects, prerequisites (e.g., element must be draggable), or return value. This is adequate for a simple action tool.

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 two short, front-loaded sentences with clear structure. Every sentence adds value without redundancy, making it concise and easy to parse.

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 9 parameters and no required ones, the description explains the core use case but omits several parameters and does not clarify what the output schema contains. It is minimally complete for an agent to use correctly, but leaves gaps.

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 coverage is 0%, so description must compensate. It explains the two parameter groups (target vs offset) and duration, but does not cover other parameters like by, tab_id, locator, or element_id. Some of these may be self-explanatory, but the description could be more thorough.

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 drags an element to a target or by pixel offset, specifying the verb 'drag' and the resource 'element', distinguishing it from sibling tools like element_clear or element_find.

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 explicitly provides usage guidance: use target_locator/target_element_id for drag-to-target or offset_x/offset_y for pixel drag, and mentions duration for speed control. However, it does not explicitly state when not to use this tool versus alternatives.

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