rotate

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It states the rotation action but omits key behavioral details such as whether the rotation is clockwise, the default for the pages parameter, output file creation behavior, or whether the source file is modified. The output_name parameter in the schema hints at output handling, but the description fails to explicitly disclose this.

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 a single, concise sentence that is front-loaded with the primary action. It contains no filler or redundant information.

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 tool has four parameters and two required fields, with no output schema or annotations to fall back on. However, the description only covers the core rotation action and does not elaborate on page range defaults, output naming conventions, or the effect on the original file, making it incomplete for an agent to use confidently.

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 input schema has 100% description coverage for all four parameters, including 'degrees' with enumerated values and 'pages' with default behavior. The description does not add any parameter-level semantics beyond what the schema already provides, so the baseline score of 3 applies.

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 specifies the action 'rotate' on 'pages in a PDF' with explicit degree values (90, 180, 270), clearly distinguishing it from sibling conversion tools like pdf_to_jpg or page manipulation tools like extract_pages.

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?

The description implies usage when rotation of PDF pages is needed, but it does not mention alternatives or when not to use it (e.g., deskew_pdf for automatic straightening). No explicit usage guidance is provided beyond the core function.

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