orientation

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

No annotations are provided, so the description carries the behavioral burden. It does disclose one useful operational trait: the command times out after 90 seconds. However, it does not mention side effects, session requirements, failure modes, or what happens to current device state, so transparency is only partial.

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 very short and front-loads the action verb. The only structural issue is the missing punctuation/space between 'Android' and 'Times', which slightly harms readability, but every word earns its place.

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 output schema exists and parameter schema coverage is strong, so return values and most parameters are already handled. Still, for a 17-parameter tool with no annotations, the description lacks usage guidance and behavioral context beyond the timeout, making it only minimally complete.

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 high at 94%, so the baseline is 3. The description adds the high-level intent of the required 'orientation' parameter, which lacks a schema description, but it does not explain orientation value semantics or how device selectors resolve, leaving the schema to carry most parameter meaning.

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 a specific action and resource: 'Set device orientation', and narrows scope to iOS and Android. It is distinct from every sibling tool because orientation is the only rotation-related command, but it does not explicitly differentiate itself from a similar sibling.

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?

There is no guidance about when to use this tool versus any alternative, nor any exclusion criteria. The only implied usage context is 'iOS and Android', but no explicit when-to-use or when-not-to-use instructions are provided.

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