pdf_to_tiff

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

With no annotations provided, the description carries the full burden for behavioral disclosure. However, it only states the basic rendering action and does not clarify important behaviors like whether multiple pages produce separate TIFF files or a single multipage TIFF, output file naming conventions, or overwrite behavior.

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, focused sentence that is front-loaded with the essential action and output. There is no unnecessary wording or repetition.

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 full schema coverage, the overall tool context is under-specified. The description does not indicate the nature of the output files (e.g., separate TIFFs per page vs. a multi-page TIFF), nor does it mention any side effects or return behavior. This ambiguity is significant for an agent deciding whether and how to use the tool.

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 parameters (dpi, file, pages, output_dir) are already fully described in the schema. The description adds no extra semantic value beyond what the schema provides, which meets the baseline of 3.

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's function with a specific verb ('Render') and resource ('PDF pages') and output format ('TIFF images'). It distinguishes itself from sibling tools like pdf_to_png or pdf_to_jpg by explicitly naming TIFF.

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?

There is no guidance on when to use this tool versus alternatives such as pdf_to_png or pdf_to_jpg. Neither the description nor annotations provide context about preferred use cases or exclusions.

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