mouse_drag

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

Annotations are neutral (readOnlyHint=false, destructiveHint=false). The description does not detail side effects (e.g., cursor movement, visual feedback) beyond the drag action. It provides basic inputs and return value but lacks behavioral context.

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 concise, using a standard Args/Returns format. It is front-loaded with the main action. However, the Python docstring style is slightly verbose for a tool description.

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 drag tool, the description provides necessary information: action, parameters, and return type. An output schema exists. No critical context is missing.

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 lists 'optional start, required end, button and duration,' summarizing the parameters. However, the schema already provides detailed descriptions for each parameter. With 0% schema description coverage from the tool description, it adds minimal new meaning 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 'Press a mouse button at a start point and release it at an end point,' which defines the tool's action of dragging. This distinguishes 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?

No explicit guidance on when to use this tool versus alternatives (e.g., mouse_click, mouse_move). The description implies dragging, but does not contrast with other input methods.

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