orientation

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action ('set orientation') without explaining side effects, persistence, whether it affects both platforms simultaneously, or what response to expect. For a mutating tool, this is a significant gap.

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 a single targeted sentence, making it highly efficient and free of fluff. While more detail could be beneficial, the brevity is acceptable for such a straightforward action, and no unnecessary words are present.

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?

Given the tool's simplicity and the existence of an output schema plus high parameter coverage, the core purpose is clear. However, the description lacks behavioral context (e.g., what happens to the device, whether it selects a specific device via params like udid/serial). It is minimally sufficient but not enriching.

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 96%, so the parameters are well-documented in the schema itself. The description adds no extra meaning beyond the action. The baseline 3 applies because the schema does the heavy lifting, and the description doesn't need to add more.

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 uses a specific verb ('Set') with a clear resource ('device orientation') and platform scoping ('iOS and Android'), which unambiguously distinguishes it from sibling tools like viewport. This is a precise, non-tautological statement of the tool's function.

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 usage context is provided. The description does not indicate when to use this tool versus alternatives (e.g., viewport), nor does it mention any prerequisites or conditions. There is no guidance on device selection or platform-specific considerations.

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