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

Annotations only declare the safety profile (readOnly=false, destructive=false, idempotent=false, openWorld=false); the description goes well beyond them with velocity validation (>6000 px/sec threshold), coordinate validation against device bounds, POINT vs pixel coordinate space, profile timing/distance values, and the caveat that newer operations require a supporting idb CLI and companion. That is exactly the kind of operational context annotations cannot convey.

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?

Well structured with headings and front-loaded purpose, but bloated: the "Complete JSON Examples" block (11 examples) and the later TypeScript "Examples" block repeat the same calls, and the h1/name echo plus emoji header add little. Much of the length is redundant rather than informative.

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 17-parameter, multi-operation tool with no output schema, the description covers operations, per-operation parameters, profile tuning, coordinate space, return payload, and error behavior, which is substantial. The remaining gap is the mismatch between the documented `profile`/operation values and the actual schema enum, which leaves ambiguity about what will actually be accepted.

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?

With only 6% schema description coverage, the description carries nearly the full burden and mostly succeeds: it documents operation values, direction, duration units, amount bounds, count, scale, source/destination, orientation, buttonType, and actionName/expectedOutcome. However it is internally inconsistent — "What it does" names profiles as flick/swipe/drag while the Parameters section says standard/flick/gentle, `profile` is documented but absent from the schema, and the Required section narrows operation to "swipe" | "button" while the schema enum and later sections add scroll, refresh, pinch, drag, rotate, shake.

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 ("Executes swipe gestures ... and hardware button presses on iOS targets") and enumerates the concrete capabilities. The Related Tools section explicitly separates it from idb-ui-tap (element tapping) and idb-ui-describe (finding coordinates), so an agent can route correctly.

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?

A dedicated "Why you'd use it" section gives concrete scenarios (reveal content, dismiss modals, test hardware buttons) and the Swipe Profiles section says which profile to pick for which UI (flick for carousels, gentle for slow scrolling). It never states when NOT to use this tool or what preconditions exist (e.g., app must be foregrounded), so it is strong but not exhaustive.

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