Rotate pages clockwise by 90, 180, or 270 degrees. Rotates all pages unless a page list is given. Returns base64.
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | The PDF file, base64-encoded (max 10 MB) | |
| pages | No | Optional page list like "1, 3"; omit to rotate all | |
| degrees | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the behavioral disclosure burden. It reveals the clockwise orientation, default page scope, and that the tool returns base64, which implies a transformation rather than an in-place modification. It could add side-effect or permission details, but the core behavior is transparent.
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?
Three tightly written sentences, each adding distinct information: the operation, the default scope, and the return format. No filler or redundant restatement.
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 simple tool with three parameters and no output schema, the description covers the key invocation details and the return type. It does not describe output structure beyond base64, but that is sufficient for an agent to call the tool and handle the result.
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 moderate at 67%, and the description adds meaning beyond the schema: it specifies clockwise direction for degrees and clarifies that omitting pages rotates the entire document. The page-list example '1, 3' gives useful concrete syntax guidance.
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 specific verb and resource: rotate pages by fixed clockwise degrees. The operation is distinct from all siblings, which handle extraction, merging, splitting, flattening, metadata, or watermarking.
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 clearly defines the default behavior (rotate all pages) and the condition for a narrower operation (provide a page list). It does not explicitly name alternatives or exclusions, but no sibling performs rotation, so the intended use is clear.
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.
Each tool targets a distinct PDF operation: page numbering, watermarking, flattening, metadata read/write, and various page selection/rearrangement tasks. Although extract_pages, remove_pages, and split_pdf all involve page ranges, their descriptions clearly differentiate extracting a subset, deleting a subset, and partitioning into multiple outputs.
All tool names follow a consistent verb_noun pattern in lowercase snake_case, such as add_page_numbers, get_pdf_metadata, merge_pdfs, and rotate_pdf. The pattern is predictable across the entire set, with no mixed conventions or vague verbs.
Ten tools is a well-scoped size for a PDF utility server. Each tool earns its place by covering a distinct common PDF manipulation task without redundancy or feature bloat.
The toolset covers core PDF operations: page extraction, removal, splitting, merging, rotation, watermarking, page numbering, flattening, and metadata read/write. Notable minor gaps include encryption/decryption and page reordering, but the provided surface handles most routine PDF workflows without dead ends.