rotate_device

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

Discloses that it waits for OS rotation animation to complete, adding behavioral context beyond annotations. Annotations (idempotentHint, destructiveHint) are consistent with description.

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?

Two concise sentences with no redundancy. Front-loaded with action and resource, followed by behavior and usage notes.

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 one-parameter tool, description covers purpose, behavior, usage, and platform constraints comprehensively. No output schema needed.

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?

Input schema fully covers parameter with enum and description; description adds no additional semantic value beyond reiterating orientation values. Baseline 3 due to 100% schema coverage.

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?

Clearly specifies verb 'rotates', resource 'mobile device', and target orientations (portrait/landscape). Distinguishes from sibling tools by focusing solely on orientation change, not other device actions.

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?

Explicitly states use case (test orientation-dependent layouts) and limitation (mobile-only, no browser effect), providing clear when-to-use and when-not-to-use guidance.

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