pdf_merge

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not mention whether the operation is synchronous or asynchronous (sibling wait_job_completion suggests it may return a job ID), what the return value looks like, required authentication (beyond schema), or any rate limits. This is a significant gap for a tool that likely submits a job.

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 core description is a single efficient sentence stating the tool's purpose and accepted input types. The second sentence is a reference link, which is compact but not strictly inline content. No fluff or repetition.

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?

The description is incomplete given the surrounding context. There is no output schema, so the description should explain what the tool returns. The existence of wait_job_completion suggests this tool may return a job ID for asynchronous processing, but the description never mentions this. An agent cannot reliably know how to consume the result without this information.

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%, so the baseline is 3. The description adds a small extra detail: support for ZIP files containing documents and images, which is not explicitly mentioned in the schema's list of supported types. No other semantic value is added 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 merges multiple file types (PDF, DOC, XLS, images, ZIP) into a new PDF. This specific verb+resource combination distinguishes it from siblings like pdf_split (splitting) and document_to_pdf (single document conversion).

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: use when you need to merge multiple files of various formats into one PDF. However, it does not explicitly state when not to use it or name alternatives (e.g., for converting a single file to PDF, use document_to_pdf instead). The guidance is implied rather than explicit.

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