set_orientation

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Rotate the screen' discloses no behavior: nothing about whether the change is persistent, whether reverse orientations are supported on all devices, what happens when an unsupported orientation is requested, or any side effects. A one-line statement is entirely insufficient for a device-mutating tool.

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 five-word sentence is technically terse, but this is under-specification rather than conciseness. There is no structure or front-loading of important constraints, and the sentence doesn't earn its place by conveying meaningful operational detail.

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 2-parameter tool with no annotations and no output schema, a single clause is grossly incomplete. Missing entirely: the meaning of each orientation enum value, when serial is required, the return behavior, and device compatibility for reverse orientations. An agent cannot call this tool correctly with confidence.

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 50% (serial has a description; orientation has only an enum with no description). The description adds zero meaning beyond the schema — it doesn't explain what each orientation value does or how serial selection works. Since coverage is borderline rather than high, the description should have compensated but does not.

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?

States a verb (rotate) and resource (the screen), giving basic purpose. However, 'rotate' implies relative motion while the schema's enum values (portrait, landscape, reverse_portrait, reverse_landscape) indicate an absolute orientation set, so the wording is mildly misleading. None of the siblings handle orientation, so it is implicitly distinct, but the description doesn't make that differentiation explicit.

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 versus alternatives. There is no mention of prerequisites, exclusions, or contexts in which set_orientation is preferred over other device-state tools like set_appearance or set_location. An agent has to infer usage entirely from the tool name.

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