mobile_gesture

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

With no annotations, the description must fully disclose behaviors, but it only says 'execute gestures' without mentioning side effects, failure scenarios, permissions, or whether it is destructive. The schema describes parameters like return_screen, but the description adds no behavioral context.

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 very concise with a single sentence that covers the core action and gesture types. However, it could be restructured to front-load key information; currently it's minimal but efficient.

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 tool with 10 parameters, no output schema, and no annotations, the description is too sparse. It lacks details on return values, error handling, and how parameters interact, making it insufficient for an agent to use reliably without additional context.

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. The description lists gesture types, which adds some context, but does not add significant meaning beyond the schema's parameter descriptions and enum values.

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 the tool executes gestures and lists specific types (tap, swipe, etc.), but does not differentiate from sibling tools like mobile_gesture_combo or mobile_gesture_macro, which may also handle multi-step sequences.

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?

No guidance on when to use this tool versus alternatives (e.g., mobile_gesture_combo, mobile_gesture_macro). The description does not specify prerequisites, when not to use, or context-dependent choices.

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