left_click_drag

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

No annotations are provided, so the description must disclose behavioral traits. It describes the basic sequence (press, drag, release) but lacks details about timing, acceleration, or what happens if start_coordinate is omitted. A more thorough description would mention edge cases or potential side effects.

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, efficient sentence with no wasted words. It front-loads the essential action and uses parentheses for optional behavior, which is well-structured.

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 tool's simplicity, 100% schema coverage, and lack of output schema, the description is largely complete. It explains the start and end points. However, it could mention that this is a mouse drag action (e.g., for moving objects) to improve intuitive understanding.

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?

Both parameters have schema descriptions with coordinate format details. The tool description adds value by noting that start_coordinate is optional and defaults to the current position, which is not fully captured in the schema alone (schema makes coordinate required but doesn't clarify start_coordinate's role).

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: pressing the left button at start_coordinate (or current position) and dragging to a target coordinate. It uses a specific verb and resource, distinguishing it from related tools like left_click, mouse_move, and left_mouse_down.

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 implies usage for drag operations but does not explicitly state when to use this tool versus alternatives like left_mouse_down + mouse_move + left_mouse_up or other click-and-drag methods. No guidance on prerequisites or when not to use.

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