image_to_pdf

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

With no annotations, the description carries the full behavioral burden. It discloses the transformation semantic (one image becomes one PDF page) and supported formats, but says nothing about overwrite behavior, whether the source image is modified, permissions, or typical failure modes on corrupt/unsupported files.

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?

Two short sentences, zero waste, with the core action front-loaded and the use case following. Nothing to trim.

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?

For a simple two-parameter conversion with full schema coverage, the description is nearly sufficient. Since no output schema exists, it could say more about what is returned or where the result lands, though output_path's schema description partially covers this.

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 both parameters (file, output_path, including the default '-papyrio.pdf' suffix) are already fully documented in the schema. The description's format list marginally enriches the 'file' parameter but adds no syntax beyond the baseline.

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 ('Wrap a ... image in a PDF page') and enumerates the accepted input formats (JPG, PNG, WebP). No sibling performs this direction of conversion (pdf_to_jpg is the inverse), so an agent can place it immediately.

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?

Gives a clear when-to-use trigger: 'when an image needs to be submitted or printed as a PDF.' It does not name exclusions or alternatives, but among the sibling set there is no competing tool for image→PDF, so the gap is minor.

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