pdf_to_images

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the conversion action but fails to mention side effects such as whether output files are overwritten, whether output_dir is created if missing, or how pages are selected and named.

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 sentence, which is concise, but it is under-specified rather than effectively concise. It provides only the core function without adding any useful detail, making it insufficient for a tool with five parameters.

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?

The tool has 5 parameters and no annotations, and although an output schema exists, the description lacks critical context about page selection, format options, and output behavior. It is not complete enough for a tool of this complexity, even considering the output schema.

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?

The description gives no explanation of the parameters (dpi, pages, format, file_path, output_dir). Schema description coverage is 0%, and the description does not compensate, leaving the agent without any semantic understanding of these options beyond their names and defaults.

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 converts PDF pages to image files, using a specific verb and resource. It is distinguishable from sibling tools like extract_text or images_to_pdf, though it lacks detail on scope (e.g., all pages vs selected 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?

The description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, use cases, or situations where another sibling tool (e.g., images_to_pdf for reverse conversion) would be more appropriate.

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