Drag between coordinates

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

The description does not disclose any behavioral details beyond the bare action, such as whether the drag includes mouse-down/move/up, how coordinates are interpreted (viewport vs page), or any side effects. The annotations only provide readOnlyHint=false and destructiveHint=false, which offer minimal insight.

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 concise sentence with no unnecessary words or repetition. It directly states the action and subject, making it highly efficient.

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 an output schema and the simplicity of the tool, the description is adequate but lacks explicit context about the coordinate system (e.g., viewport-relative vs page-relative) and whether a drop event is included. It does not fully prepare an agent for edge cases or expected behavior.

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 schema descriptions cover all four parameters (Start X, Start Y, End X, End Y), so schema coverage is 100%. The tool description adds no additional meaning beyond rephrasing 'from one viewport coordinate to another,' which aligns with the parameter names but does not enrich understanding of coordinate semantics or units.

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 resource ('viewport coordinate to another'), making the tool's purpose understandable. However, it does not explicitly distinguish itself from sibling tools like 'browser_drag' or 'browser_mouse_move_xy', so the differentiation is implicit rather than explicit.

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 no guidance on when to use this tool versus alternatives, such as 'browser_drag' for element-based dragging or 'browser_mouse_move_xy' for moving without dragging. No conditions or use cases are mentioned.

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