left_click_drag

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

With no annotations, the description carries the burden of explaining the behavior. 'Click and drag' conveys the basic press-move-release action but does not explicitly mention that it uses the left button, what happens when start_coordinate is omitted, or whether the movement is smooth/instant. These are partially recoverable from the name and schema, but the description alone is thin.

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, front-loaded sentence with zero waste. Every word contributes to understanding the action and the two key coordinates involved.

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?

For a simple primitive with no output schema and complete parameter descriptions, the combination is mostly adequate. However, the absence of annotations leaves behavioral details such as default start position and button specificity only implicit; an agent would benefit from an explicit note about the optional start_coordinate behavior in the main description.

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 description coverage is 100%, and both parameters are already documented with start position and destination semantics. The description restates the start-to-destination relationship without adding new constraints, formats, or edge-case details, so it adds little beyond the schema.

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 states a specific action (click and drag) on the mouse, with explicit start and destination points, which clearly distinguishes it from sibling tools like left_click, mouse_move, and scroll. The phrase 'from start_coordinate to coordinate' leaves no ambiguity about what the tool does.

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?

There is no explicit guidance about when to use this tool versus alternatives like mouse_move or left_click; the intended usage is implied by the drag action itself. It does not name any siblings or exclusions, so an agent must rely on its own reasoning about what 'drag' means.

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