drag

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

With no annotations, the description carries the full burden for behavioral disclosure. It does not explain how the drag is performed (e.g., mousedown/mousemove/mouseup sequence), what happens on failure, or effects of distance/duration. The only behavioral hint is the mode selection, which is already in the schema.

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 four short, front-loaded sentences. No filler words; each sentence adds actionable information (purpose, use cases, mode guidance, alternative tool). Excellent structure for quick comprehension.

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 drag tool with no output schema and no annotations, the description provides essential usage context but lacks depth on behavioral nuances (e.g., coordinate origins, supported element types, error cases). It is adequate but leaves gaps that a more detailed description could fill.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining when to use 'synthetic' mode (JS libraries) and mentions scrollHorizontal as an alternative for scrollbars, enriching the understanding of parameters like mode and direction.

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 'Drag element in any direction' with specific use cases (maps, charts, SVG, canvas, sliders), distinguishing it from sibling tools like scrollHorizontal and click. The verb and resource are specific and unambiguous.

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?

Provides concrete usage guidance: use mode='synthetic' for JS libraries and use scrollHorizontal for scrollbars. This clarifies when to use this tool versus alternatives, though it doesn't explicitly list all exclusion cases.

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