drag

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

The description explains the core behavior (mouse-down, move, up) but omits details about button, speed, waiting, or edge case handling. With no annotations, more behavioral context would be helpful.

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 concise sentence that front-loads the key purpose and mechanism. It achieves clarity without unnecessary words, though it could be expanded slightly to cover parameters.

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 8 parameters, 0% schema coverage, and no output schema, the description is incomplete. It does not explain optional parameters, return behavior, or prerequisites, leaving significant gaps for an agent to use the tool correctly.

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 explains x1,y1,x2,y2 implicitly but does not cover optional parameters like button, observe, instance, or settle_ms. Schema description coverage is 0%, so the description should compensate but fails to do so.

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 (drag) and the resource (mouse coordinates), and distinguishes from siblings by specifying the sequence (mouse-down → move → up) and use cases (drawing shapes / selecting). It is specific and informative.

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 use for drawing or selecting, but does not explicitly state when to use this tool versus alternatives like click or move_mouse. No when-not-to-use or alternative tool names are provided.

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