set_page_orientation

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

With no annotations, the description carries the transparency burden. It discloses the swapping behavior and para_id handling, but lacks details on side effects (e.g., scaling content, interaction with other properties) or auth requirements.

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 concise: two sentences plus a brief arg list. Every sentence adds value, and the key information is front-loaded. No redundancy or fluff.

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 output schema exists (not shown but present), the description is adequate for a simple tool. It covers all parameters and the core behavior. Minor gap: no explanation of return value or success/failure indicators, but output schema likely fills that.

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?

The description adds significant meaning beyond the schema: orientation is explained as 'portrait' or 'landscape', and para_id is described as 'paraId of paragraph with section break. None = body section.' Schema coverage is 0%, so this is essential context. However, it could further specify allowed values or constraints.

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 tool's function with specific verb and resource: 'Set page orientation, swapping width/height dimensions if needed.' This is distinct from siblings like set_page_size or set_section_properties, and the purpose is immediately understandable.

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 explicit guidance on when to use this tool vs. alternatives (e.g., set_page_size, set_section_properties). The description implies section-level usage via para_id but does not specify when one should choose this over other formatting tools.

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