rotate_device

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

Annotations include destructiveHint=false but no readOnlyHint, so the mutation is implied by the annotation absence. The description adds the 'requires active scrcpy session' prerequisite, which is useful context. However, it doesn't disclose whether rotation affects alpha/beta versions, whether the change persists, or what the return value contains.

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 concise sentence with zero wasted words. The prerequisite information is packed efficiently into the parenthetical. Ideal length for a simple single-parameter tool.

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?

The tool is simple with one optional parameter and a required-session prerequisite clearly stated. The output schema exists so return value explanation isn't needed. For its complexity level, the description covers what's necessary.

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 100% with the single 'serial' parameter described as 'Device serial number', which is adequate for an optional/contextual parameter. The description doesn't add meaning beyond the schema, but with full coverage and a single obvious parameter, the baseline 3 is appropriate.

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 verb (Rotate) and resource (device screen), distinguishing it as an action on the device display. It's unambiguous in purpose and distinguishes from siblings like screen_on/screen_off which control screen power rather than orientation.

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 parenthetical '(requires active scrcpy session)' gives clear context that an active session must exist, implying it belongs within the scrcpy session workflow. It doesn't explicitly name alternatives or when-not-to-use, but the prerequisite is valuable guidance.

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