drag

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — not whether it needs focus, whether the drag is visible, or how timing/button affect behavior. No contradiction with annotations.

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?

Four characters are technically concise, but this is under-specification rather than economy. There is no waste, yet nothing is front-loaded because there is nothing to load.

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?

A GUI automation tool with six parameters, four of them required and none documented by the schema, demands far more than "press and drag." The agent cannot determine coordinate semantics, button defaults, or drag duration from this definition.

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 0% across six parameters. The description does not explain that x0/y0 is the start point and x1/y1 the end point, whether coordinates are screen or window relative, what values 'button' accepts, or what 'seconds' controls.

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?

"按住拖动" (press and drag) names a specific action and implicitly distinguishes itself from the sibling "move" by indicating the button is held down. However, it never states that it drags from one point to another, nor what it operates on (desktop, window, element).

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 guidance on when to use this instead of the sibling tools move, click, or scroll, and no prerequisites or exclusions are mentioned. The agent must infer everything from the name alone.

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