pdf_to_images

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotence, so the safety profile is covered. The description adds real value with the external ghostscript dependency, but it never explains what overwriting means, whether existing files in output_dir are clobbered, or failure behavior for a destructive write tool.

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, transformation stated first, constraint appended. No filler, no restating of the tool name.

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 six parameters at 0% schema coverage and a destructive write profile, the description leaves page-range syntax, overwrite semantics, and output naming conventions undefined. The output schema does relieve it of explaining return values, but the input-side gaps remain substantial.

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 0%, so the description must carry parameter meaning, but it only glosses format (PNG/JPEG), DPI, input PDF, and output folder. It says nothing about the "pages" parameter's syntax for selecting page ranges or what "overwrite" actually governs.

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 transformation ("Render PDF pages to PNG or JPEG files") plus the output medium (a folder) and quality control (chosen DPI), which cleanly separates it from siblings like pdf_info, pdf_extract_text, and image_convert. It does not explicitly name the alternative tools an agent might confuse it with.

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 a dependency note ("Needs ghostscript") but no statement of when to pick this over pdf_extract_text, ocr_image, or image_convert, and no exclusions. An agent must infer usage entirely from the one-line purpose.

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