swipe_screen

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state which app/device state is required, whether the gesture interpolates intermediate points, how duration affects the outcome, or what the tool returns, leaving the mutation's behavior largely opaque.

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?

A single short sentence, front-loaded with the action, with no filler. The only inefficiency is the second clause, which duplicates information already implied by the parameter names.

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?

An output schema exists, so return values need not be described, and the 100%-covered schema handles the parameters. The remaining gap is the absence of any usage context or behavioral notes in a tool with zero annotations, which leaves the definition only minimally sufficient.

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% and every parameter (x1, y1, x2, y2, duration_ms) is individually documented in the schema, so the baseline is 3. The description adds no coordinate-format or duration-tuning meaning beyond what the schema already supplies.

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?

States a specific verb (执行滑动) and resource (屏幕), making the swipe gesture unambiguous next to siblings like tap_screen and long_press. However, the trailing clause '从起点滑动到终点' merely restates the required coordinate parameters and adds no differentiating information.

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 gives no guidance on when to swipe versus tap_screen or long_press, nor does it mention that duration_ms controls gesture speed (e.g., a fast flick vs. a slow drag). The agent must infer all usage context.

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