Split a PDF into multiple files by page ranges, or extract every page as a separate file. Specify ranges like 1-3;4-6;7- to control output.
Split a PDF into several files.
ranges: semicolon-separated page specs, one file each, e.g. "1-3;4-6;7-". If omitted, every page becomes its own file.
| Name | Required | Description | Default |
|---|---|---|---|
| ranges | No | ||
| password | No | ||
| overwrite | No | ||
| input_path | Yes | ||
| output_dir | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It states output cardinality—one file per range, otherwise one file per page—but omits overwrite behavior, password handling, output naming, and whether the original file is modified.
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 short, front-loaded, and includes a concrete example. Every sentence supports range formatting or default behavior, with no filler.
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 five-parameter tool with no annotations, no output schema, and zero schema descriptions, the definition is incomplete. It covers the most distinctive parameter but leaves overwrite/password/output behavior and error expectations unstated.
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 0%, and the description only documents the ranges parameter, including its semicolon syntax and default. It does not explain password, overwrite, input_path, or output_dir semantics, leaving most parameters to inference.
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 opens with a specific verb and resource: "Split a PDF into several files." That lets an agent distinguish it from merge_pdfs and extract_pages by the multiple-output outcome, though no sibling is named explicitly.
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?
It explains the ranges format and the default when ranges is omitted, which helps with invocation. However, it does not state when to choose split_pdf over extract_pages or merge_pdfs, nor does it mention prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.