Convert Anything to PDF

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

With no annotations, the description carries the full burden and does so thoroughly: it lists all 36 accepted extensions, discloses that PDF inputs are passed through, describes the return shape (presigned URL, metadata, jobId), and details the pdf_options caveat that geometry options only apply to certain input types, with a 400 rejection for unsupported combinations.

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 well-structured with front-loaded purpose and clear section headers, and every major piece of content is useful. However, it is somewhat longer than necessary because format lists like images, SVG, and RTF appear both in the 'Use when' examples and again in the overlap explanation, creating mild redundancy.

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?

Given no output schema and no annotations, the description is remarkably complete: it covers input path/URL, accepted extensions, return values, exclusions, alternatives, and pdf_options limitations. The only omission is explicit sync/async behavior, but the jobId return value strongly implies asynchronous processing.

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 baseline is 3. The description adds meaningful value beyond the schema by explaining the pdf_options geometry caveat and the absolute-path requirement, but it does not enrich every parameter; save_to and output_filename rely mostly on their schema descriptions.

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 opens with a specific verb and resource: 'Convert almost any FILE to PDF' and explicitly frames the tool as a catch-all endpoint. It distinguishes itself from convert_document, convert_image, perceive_url, and convert_anything_to_markdown by describing its unique scope.

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 explicit 'Use when' and 'Do NOT use when' sections, including named alternatives (perceive_url, convert_document, convert_anything_to_markdown) and clear reasoning for when the catch-all is preferable. It even explains the deliberate overlap with convert_document and which side of that overlap to choose.

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