Rotate PDF — Rotate pages of a PDF by 90, 180, or 270 degrees — all pages or specific page numbers. [category: pdf]
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | Input PDF (max 25MB) | |
| pages | No | Which pages to turn, e.g. '1-3,5'. Leave blank to turn every page. | |
| rotation | No | How far to turn each page, clockwise. | |
| outputName | No | Optional custom output filename. |
Changes observed during successful MCP inspections.
Input schema / properties / pages / titleAdded value: +"Pages to rotate"Input schema / properties / pages / x-uiAdded value: +{
+ "no_recall": true,
+ "page_select": {}
+}Input schema / properties / pages / descriptionPrevious value: -"Page ranges e.g. '1-3,5'. Empty = ALL pages — do NOT send 'all'."New value: +"Which pages to turn, e.g. '1-3,5'. Leave blank to turn every page."Input schema / properties / rotation / descriptionPrevious value: -"Degrees clockwise. The field name is 'rotation' — not 'angle'."New value: +"How far to turn each page, clockwise."Input schema / properties / rotation / x-uiAdded value: +{
+ "labels": {
+ "180": "180° (upside down)",
+ "270": "90° anticlockwise",
+ "90": "90° clockwise"
+ }
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false and destructiveHint=false, so the agent knows this is a mutating but non-destructive operation. The description adds useful operational detail (degrees and page selection) but does not state whether the original file is overwritten or a new file is returned, nor does it describe the output. There is no contradiction with the annotations.
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, front-loaded sentence with no filler. It immediately conveys the action, the valid degrees, and the page-scope options. The trailing category tag is unobtrusive and useful.
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?
There is no output schema, so the description should indicate what the tool returns (e.g., a rotated PDF file). The core operation and page options are present, but return-value behavior and routing among the many PDF siblings are not covered. For a straightforward single-file transform this is adequate, though not complete.
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 100%, so all parameters are already documented. The description paraphrases the `rotation` and `pages` parameters but adds no information beyond the schema, such as how page ranges are parsed or the default rotation value.
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 identifies a specific action ('Rotate pages of a PDF'), the resource (PDF), and the operational scope (by 90, 180, or 270 degrees; all pages or specific page numbers). This makes the tool's purpose unambiguous. However, it does not explicitly contrast with sibling tools like pdf_reverse or pdf_reorder, so sibling differentiation remains implicit.
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?
There is no guidance on when to choose pdf_rotate over related operations such as pdf_reverse (page order), pdf_reorder, or photo_flip_rotate (image rotation). The only usage signal is the name and the first clause; no exclusions or named alternatives are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.