images_to_pdf

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

No annotations are provided, so the description carries the burden. It discloses a key behavioral trait: each image is placed on its own PDF page with 'perfect fill and no whitespace'. However, it does not mention potential side effects like overwriting existing files, page size, or aspect ratio handling.

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 sentence with the key information, no fluff, and the action is front-loaded. Every clause serves a purpose, making it highly concise and well-structured.

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, the description covers the core function but leaves gaps: parameter details are absent, and it does not mention behaviors like overwriting output or supported image formats. It's adequate but not comprehensive, especially with no annotations or output schema.

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 includes imagePaths and outputPath, but the description adds no explanation for these parameters. With 0% schema description coverage, the description should compensate, but it only names the conversion, leaving parameter semantics to be inferred from their self-explanatory names.

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 verb 'convert' and resource 'multiple images to PDF', with specific scope details 'one per page, perfectly filled without whitespace'. This distinguishes it from the sibling images_to_pptx by the output format (PDF vs PPTX).

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 when a PDF output is needed, but it does not explicitly mention when to use this tool over the sibling images_to_pptx or any exclusions. It provides clear context but lacks alternative guidance, so it receives a 3.

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