element_swipe

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

Describes the gesture sequence, default parameters (distance 60% of element width/height, duration 300ms, start at center), and extra wait time. No annotations provided, so description carries the burden; no contradictions.

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?

Single paragraph with front-loaded purpose and parameter list. Efficient but dense; could be structured with bullet points for readability. No wasted words.

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?

Adequate for a swipe tool with 10 parameters and no output schema. Covers purpose, usage guidance, and parameter details. Does not mention return values or errors, but not required given lacking output schema.

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?

Adds meaning beyond schema by explaining direction enum, distance default, duration default, start coordinates default, waitMs, innerSelector, and selector index support. Schema coverage is only 10%, but description compensates well.

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 real swipe gesture (touchstart→touchmove→touchend), specifies use case (lists, carousels, draggable areas), and distinguishes from sibling element_touch by recommending this tool for simplicity.

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 to prefer this tool over element_touch for simple swipes and indicates suitable scenarios. However, does not specify when not to use it or mention alternatives.

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