mouse_drag

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

The description does not disclose that the drag may disrupt focus or require explicit user consent, despite the confirm_focus_disruption parameter in the schema. Annotations provide little behavioral context (readOnlyHint=false, destructiveHint=false), so the description carries the burden and falls short.

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 compact and well-structured with an action summary followed by Args and Returns sections. Every sentence is informative, with no filler or redundancy.

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?

While the description explains the basic operation, it lacks important context about when confirm_focus_disruption should be set and what happens when start is omitted (the schema explains this, but the description does not). The rich schema partially compensates, but the description alone is not fully complete for safe and correct usage.

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 description gives a high-level summary of arguments (start, end, button, duration), but the schema already provides detailed descriptions for all properties. The description omits confirm_focus_disruption, and the summary is slightly ambiguous about which parameters are optional. It adds minimal value 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 clearly states the action: 'Press a mouse button at a start point and release it at an end point.' This verb+resource phrasing distinctly differentiates it from sibling tools like mouse_click, mouse_move, and mouse_scroll.

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 it is used for dragging but does not explicitly discuss when to use it instead of alternatives such as a mouse_move followed by a mouse_click. No exclusion criteria or alternative tools are mentioned.

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