Images to PDF

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

Annotations already declare non-read-only, non-destructive, idempotent behavior, so the safety profile is covered. The description usefully adds that page count and ordering follow the input list, but says nothing about failure modes, the no-overwrite constraint, or the 200-image ceiling beyond what the schema states.

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 16-word sentence with no filler, front-loading the action and then the two behavioral guarantees in the same breath.

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?

An output schema exists, so return values need no explanation, and annotations cover the mutation/idempotency profile. The remaining constraints (allowed folders, non-existent output path, max items) live in the schema, leaving nothing an agent needs missing from the definition.

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?

With schema description coverage at 50%, the description does add meaning by clarifying that the order of the inputs array maps directly to page order. It adds nothing about the output path semantics (must not exist, no overwrite), though that is documented in the schema itself.

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?

States a specific verb and resource (make a PDF from JPG or PNG images) and adds the two defining behaviors: one page per image and input-order preservation. The image-only input format naturally distinguishes it from the pdf_from_office and pdf_from_markdown siblings.

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?

Usage is implied by the tool name and the format constraint, so an agent can infer it is the right tool when source material is a set of images. However, no explicit when-to-use or when-not-to-use guidance, and no alternatives are named.

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