Rewrite a PDF's document properties. Pass empty strings to strip identifying metadata before sharing. Returns base64.
| Name | Required | Description | Default |
|---|---|---|---|
| file | Yes | The PDF file, base64-encoded (max 10 MB) | |
| title | No | ||
| author | No | ||
| creator | No | ||
| subject | No | ||
| keywords | No | Comma-separated | |
| producer | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It discloses the tool's mutating/transformative nature, the empty-string stripping behavior, and the base64 return format. It does not cover side effects or error handling, but the essential agent-relevant behavior is present.
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 two short sentences with no filler. It front-loads the core action, then adds a practical usage tip and the return format. Every clause earns its place.
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 low schema coverage and lack of output schema, the description covers the return format and a main use case, which is sufficient for basic invocation. However, it leaves ambiguity about what happens when optional metadata parameters are omitted and does not explicitly orient the agent toward get_pdf_metadata as the read counterpart.
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 low at 29%, but the description adds one important value-level semantic: empty strings strip metadata. Parameter names like title, author, and keywords are self-explanatory, and the schema documents file and keywords format. The description partially compensates for the coverage gap but does not explain omitted-parameter behavior.
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 states a specific action ('Rewrite') on a specific resource ('PDF's document properties'), which clearly defines the tool's function. This also differentiates it from siblings like get_pdf_metadata and the page-manipulation tools without needing to open their schemas.
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 provides a concrete use case: 'Pass empty strings to strip identifying metadata before sharing.' However, it does not explicitly say when to prefer this tool over get_pdf_metadata or mention alternatives, so the routing guidance is only implied rather than stated.
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.