gesture-drag

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

No annotations provided, but description fully discloses behavior: press-start, move, release, interpolation at ~60fps, normalized coordinates, return value {dragged: true, timestampMs}, and failure condition when CDP session unreachable. Also clarifies it does not scroll.

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?

Three concise sentences: action, use cases with exclusions, return and failure. No unnecessary words, front-loaded with essential information.

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?

Description covers inputs (normalized coords, duration), behavior (interpolation, no scroll), platform specificity (Chromium desktop only), return value, failure condition, and references sibling tools. Without output schema, it sufficiently explains the return format.

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 100%, so baseline is 3. Description adds context about normalized coordinate space and alignment with gesture-tap and describe, but no new parameter-specific details beyond schema. Slight improvement justifies a 4.

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?

Description clearly states it performs a desktop mouse drag in a Chromium app, with specific verb 'press, move, release' and resource 'mouse drag'. It distinguishes from siblings like gesture-scroll and gesture-swipe by stating use cases and exclusions.

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?

Explicitly says when to use (slider thumbs, drag-and-drop, text selection, draggable UI) and when not to (scrolling, non-Chromium platforms). Directs to alternatives gesture-scroll and gesture-swipe.

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