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

With annotations already declaring non-read-only, non-destructive, and idempotent behavior, the description adds substantial context beyond the structured fields: it disables AUTO-ROTATE as a persistent side effect and explains why. It also states that the call returns only after the stream reports the new frame size, which affects subsequent tap mapping.

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 purpose is front-loaded, and each following sentence earns its place by covering enum semantics, the important AUTO-ROTATE side effect, and return timing. There is no filler or redundant phrasing.

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 two-parameter Android orientation tool with no output schema, the description covers the action, enum meanings, side effects, and call-completion timing. Combined with annotations and schema, an agent has everything needed to invoke it correctly.

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%, so the baseline is 3. The description adds meaningful enum semantics by mapping PORTRAIT/LANDSCAPE to iOS equivalents and explaining the 180° reverse variants, though it does not add detail for the udid parameter beyond what the schema already provides.

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 opens with a specific verb and resource: 'Set the screen orientation of an Android device.' It distinguishes Android behavior from the sibling ios_orientation and specifies which orientation enum values mirror iOS versus which are Android-only reverse variants.

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 references the iOS counterpart and explains sequencing with device_tap, but it does not explicitly say when to use device_orientation instead of other siblings such as device_rotate. Usage is implied rather than contrasted with alternatives.

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