Merge multiple PDF files into one. The user can reorder files before downloading. All processing happens locally in the user's browser. Połącz kilka plików PDF w jeden; kolejność można zmienić przed pobraniem; pliki nie opuszczają przeglądarki.
| Name | Required | Description | Default |
|---|---|---|---|
| files | No | PDF files from the conversation to merge, in order |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses local processing and that files remain in browser, which is critical for privacy. Adds reordering capability beyond basic merge.
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?
Contains unnecessary Polish duplicate text that adds no value for English context; could be half as long.
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?
Explains core functionality and privacy, but lacks details on output, file size limits, or progress feedback.
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 describes 'files' parameter; description adds that user can reorder before download, providing operational context beyond schema.
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?
Clearly states 'Merge multiple PDF files into one' and mentions reordering, distinguishing it from siblings like split_pdf and sign_pdf.
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?
Implies usage context (reordering, local processing) but no explicit when-to-use or when-not-to-use compared to alternatives.
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 has a clearly distinct purpose: filling forms, merging documents, signing, and splitting pages. There is no ambiguity or overlap between them.
All tool names follow a consistent verb_pdf_noun pattern using snake_case, making them predictable and easy to understand.
With only 4 tools, the server is well-scoped for a PDF manipulation toolkit, covering essential operations without unnecessary bloat.
The set covers common PDF tasks (fill, merge, sign, split), but is missing potential operations like compression or conversion, though these are not essential for the core purpose.