pdf_images_to_pdf

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

No annotations are provided, so the description must cover behavioral traits. It states images are scaled and become pages, but does not disclose whether existing output files are overwritten, if there are limits on image dimensions, or error handling for unsupported formats. Basic behavior is clear but lacks depth.

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?

A single, well-structured sentence that conveys purpose and key behavior without verbosity. Every word contributes value, making it easy to parse quickly.

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 (4 parameters, no output schema, no annotations), the description covers the core functionality but misses details: image order (array order), overwrite behavior, and potential size/format limits. Adequate but not fully comprehensive.

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 coverage is 100% with each parameter described. The description adds global context ('scaled to fit') but no additional parameter-level details. The margin and pageSize parameters already have clear descriptions in the schema, so the description does not significantly enhance understanding 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 verb 'Convert' and the resource 'images into a PDF', specifying supported formats (PNG/JPG) and behavior (each image becomes a page, scaled to fit, aspect ratio maintained). This distinguishes it from sibling tools like pdf_create (blank PDF) and pdf_add_image (add to existing 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?

No explicit guidance on when to use this tool vs alternatives. With siblings like pdf_add_image, pdf_merge, pdf_create, the description omits any criteria for choosing this tool, such as 'Use when you have multiple images to convert as separate pages'.

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