tiff_to_pdf

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

No annotations are provided, so the description carries the full burden. It only states the basic conversion action but does not disclose important behaviors such as handling of multi-page TIFFs, output file naming/overwrite behavior, or any side effects on the input file.

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, clear sentence with no fluff or redundant information. It is front-loaded and efficiently conveys the core purpose.

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 tool with 2 parameters and no output schema, the description is minimally adequate but lacks critical details such as multi-page TIFF handling and exact output output (whether it creates a single-page PDF or multiple). The schema error adds to the incompleteness.

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 the baseline is 3. The tool description adds no parameter-specific meaning beyond the schema. However, the schema's description for 'file' incorrectly says 'Absolute path to the PDF file', which is misleading for a TIFF input, but this is not the tool description's fault, so it does not lower the score further.

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 'Convert a TIFF image to a PDF page' clearly states the specific verb (convert), the input resource (TIFF image), and the output (PDF page). This distinguishes it from sibling tools like pdf_to_tiff (reverse direction) and other image-to-PDF converters such as png_to_pdf or jpg_to_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?

The description provides no guidance on when to use this tool versus alternatives like image_to_pdf or pdf_to_tiff. There are no prerequisites, exclusions, or context about preferred scenarios.

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