Convert PDF to Images

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

Annotations already declare it is not read-only, not idempotent and open-world, and the description usefully adds quota-relevant behavior ('counts as one conversion'), the upload destination, the 100-page limit, and the ZIP output shape. It stops short of describing failure modes or error behavior for invalid/encrypted PDFs.

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?

Four short, front-loaded sentences with no filler: rendering behavior, output artifact, page limit, then quota/upload. Every sentence carries information an agent would otherwise lack.

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?

With no output schema, the description still explains the return artifact (ZIP with one image per page), the resolution, the page cap, and the quota cost, while the schema covers all four parameters. An agent has what it needs to call this correctly.

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 format, password, input_path and output_path are fully documented in the schema; the description adds no parameter-level detail beyond the output-format implication. Baseline 3 is appropriate when the schema does the heavy lifting.

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 names a specific verb (renders) and resource (each page of a PDF as an image) plus concrete parameters of the output: 150 DPI, one image per page, delivered as a single ZIP archive. This clearly separates it from siblings like convert_pdf_to_word and extract_pdf_pages.

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?

Usage is only implied by the tool's function; there is no statement of when to choose this over extract_pdf_pages or convert_to_pdf, and no exclusions or prerequisites beyond noting the 100-page cap. Adequate but with a clear routing gap.

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