device_rotate_gesture

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

With no annotations, the description carries the full burden. It discloses that the tool is Android-only, uses UIAutomation, requires no root, and defines rotation direction. This is meaningful behavioral context for an action tool, though it does not mention failure behavior or return value.

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 three tight sentences with no filler. The core action is front-loaded, followed by the most decision-relevant details: direction and platform constraint.

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 simple gesture tool, the description and schema together cover the essential information: what it does, platform, direction, and required parameters. It could be more complete by mentioning the expected outcome or how failures surface, but nothing critical is missing for tool selection.

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 coverage is 71%, so most parameters are already described. The description adds the Android-only constraint relevant to the platform parameter, and 'two-finger' clarifies the role of center and radius. However, it mostly repeats the degrees direction already present in the schema.

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 states a specific verb and resource: 'Perform a two-finger rotation gesture' with concrete examples (rotate a map or image). This clearly distinguishes it from sibling gesture tools like device_pinch and device_swipe.

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 gives clear usage context: use for two-finger rotation, with examples, and it explicitly restricts the tool to Android ('Android only'). It does not name alternatives or say when to prefer another gesture tool, but the platform and gesture type are well specified.

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