pdf_merge

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

The description adds valuable behavioral context beyond annotations: it specifies that AcroForm fields are preserved and auto-renamed on collision, and describes the flatten option effect. Annotations indicate idempotentHint true, which is consistent, but the description provides non-obvious details.

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 sentences long, directly states the main purpose, and front-loads the essential behavior. Every sentence adds value without unnecessary verbiage.

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 tool's simplicity, full schema coverage, and no output schema, the description sufficiently covers key behaviors (form field handling, flattening). It provides enough context for an AI agent to use the tool correctly.

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?

The input schema has 100% description coverage for all parameters, so the description adds little new meaning. It repeats the flatten behavior but does not enhance understanding of filePaths or outputPath beyond the 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?

The description clearly states the tool's purpose: merging multiple PDF files into one. It uses specific verbs and resources, and the behavior (preserving AcroForm fields, flatten option) distinguishes it from sibling tools like pdf_split or pdf_create.

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 explains how to use the tool (merging, preserving AcroForm, flatten option) but does not provide explicit guidance on when to use this tool versus alternatives. It lacks comparisons to siblings like pdf_add_page_numbers or pdf_fill_form.

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