rotate

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

The description only repeats the tool's name effect without disclosing behavioral traits such as whether it affects the display orientation, sensor state, or app lifecycle. With no annotations, the description should provide more context about behavior, side effects, or platform specifics.

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, which is concise but lacks substance. It does not front-load key information beyond the basic action. While brevity is valued, this sentence is too terse to be maximally helpful.

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 complexity (24 parameters, 1 required, output schema exists), the description is insufficient. It does not explain how rotation works across platforms, what the orientation parameter values mean, or any interaction with other device states. The presence of an output schema reduces the need to explain return values, but behavioral context is still missing.

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 schema already documents parameters well. The description adds no additional meaning beyond 'rotate device orientation', which is redundant with the tool name. The required 'orientation' parameter is an enum, but the description does not elaborate on its role or format.

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 action (rotate) and the resource (device orientation), making the tool's purpose unambiguous. It distinguishes from sibling tools like click, scroll, swipe, etc., which have different functionalities.

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 guidance on when to use this tool vs alternatives. There is no mention of prerequisites, context, or exclusions. The description lacks any usage scenario or comparison with other tools.

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