pt_swipe

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

No annotations are supplied, so the description carries the full disclosure burden. It accurately conveys that a swipe gesture is performed, but does not add behavioral details such as coordinate origin, gesture speed, or potential system interactions beyond the schema's duration note.

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 two sentences, front-loaded with the action, and contains no redundant words or information that duplicates the schema.

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 the tool's simple nature and the complete parameter schema, the description provides sufficient information about purpose and usage. It does not describe return values (no output schema), which is acceptable. Minor missing context like coordinate origin is not critical.

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 input schema covers all parameters with descriptions (100%), so the description adds no additional parameter semantics; it only generically refers to 'one point to another', which is already represented by x_start/y_start/x_end/y_end.

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 a specific action ('Swipe') and the target ('the screen'), and provides common use cases (scrolling, dismissing, navigating) that differentiate it from sibling tools like pt_tap and pt_type_text.

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?

It explicitly says 'Use for scrolling, dismissing, or navigating between screens', giving clear when-to-use context. It does not mention alternative tools directly, but the sibling names (pt_tap, etc.) provide implicit alternatives.

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