images-to-pdf

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

No annotations are provided, so the description carries full behavioral burden. It only states the conversion action and does not disclose output behavior, such as whether multiple images produce separate PDFs or are merged (mergeAfter), naming conventions, or safety (e.g., whether original files are modified).

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 concise sentence with no redundancy. It is front-loaded and easy to parse, but given the tool's parameter complexity, it is perhaps overly terse; still, it earns a high score for conciseness.

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?

Despite 100% schema coverage, the description lacks context about tool behavior and usage scenarios. The agent must infer when to use this conversion, what output is created by default, and how parameters like mergeAfter affect the result. The lack of annotations and output schema further reduces completeness.

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 schema already provides descriptions for all 7 parameters, achieving 100% coverage. The description adds no parameter-specific detail beyond the schema, so it meets the baseline for high coverage.

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 converts images (JPG, PNG, etc.) to a PDF document, providing a specific verb, resource, and target format. This distinguishes it from siblings like office-to-pdf or html-to-pdf, which handle different input types.

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 guidance is given on when to use this tool versus alternatives. It lacks exclusions, prerequisites, or references to sibling tools that handle other formats (e.g., office-to-pdf). Only the schema hints at usage, not the description.

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