merge-pdfs

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic merge action and does not mention side effects, whether input files are modified, how output is created, or any permissions or error conditions. This is a significant transparency gap for a tool that clearly creates a new file.

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, clear sentence that is front-loaded and contains no unnecessary words. It efficiently communicates the core purpose without padding.

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 3 parameters and no output schema, the description is minimally adequate. It covers the primary action but omits details like default output behavior, file ordering, and error handling. These gaps lower completeness below what would be considered mostly or fully 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%, with each parameter already having a description (e.g., files as 'Array of PDF file paths or URLs to merge', outputDir, outputFilename). The tool description adds no additional parameter semantics beyond the schema, so the baseline of 3 is appropriate.

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 clearly states the tool's function: 'Merge multiple PDF files into a single PDF document'. It uses a specific verb (merge) and resource (PDF files), and the outcome (single PDF) is explicit. This distinguishes it from sibling tools like split-pdf or rotate-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?

The description implies usage: if a user needs to combine PDFs, this is the tool. However, it provides no explicit guidance on when to use this vs alternatives, no exclusions, and no mention of when not to use it. The usage context is only weakly implied by the tool name and description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.