set_page_orientation

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

The description mentions 'swapping width/height dimensions if needed', which is a behavioral detail. However, it does not disclose potential side effects (e.g., affecting all sections vs one) or required permissions. No annotations are provided to compensate.

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 extremely concise with only two sentences plus an Args block. Every word is necessary; no fluff. The structure uses a clear heading and bulleted parameters.

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 (2 params, no annotations, has output schema), the description covers the essential parameter meanings and behavioral note about dimension swapping. It could mention validation or fallback behavior but is largely sufficient.

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?

With 0% schema description coverage, the description fully compensates by explaining orientation as 'portrait or landscape' and para_id as 'paraId of paragraph with section break. None = body section.' This adds critical meaning beyond the schema's type definitions.

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 'Set page orientation' with a specific verb and resource. It distinguishes from related sibling tools like set_page_size and set_page_margins by focusing on orientation and dimension swapping.

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 like set_page_size or setting section properties. There is no mention of prerequisites or context for the orientation change.

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