create_images_from_pdf

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

With no annotations, the description carries the full safety and side-effect burden. It clearly states that the tool writes one file per page to output_dir (defaulting to the input directory), and explains the nuanced page-selection behavior (top-level pageNrs vs imageAction.PageSelection.PageNrs). This goes beyond the schema and adds meaningful behavioral context.

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?

Three sentences, each carrying unique information: API identity, controllable parameters, and output behavior. No redundant loops over the schema descriptions. It is dense but well-structured and easy to scan.

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 the tool has 5 params, no output schema, and no annotations, the description covers the core behavior (output files, default dir) and the most complex parameter interaction (page selection). It does not explain return values, but since there is no output schema, this is not required. It might benefit from a mention of overwriting behavior, but overall it is sufficiently complete for a conversion 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 coverage is 80% and the schema already describes each parameter, but the description adds important cross-parameter semantics: it explains how page_number maps to both top-level pageNrs and imageAction.PageSelection.PageNrs, and the special 'all' behavior. It also clarifies that width_pixel and image_extension map to imageAction fields, which is not evident from the schema alone.

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 starts with a specific verb+resource: 'Render PDF pages to image files', which clearly distinguishes this tool from siblings like convert_pdf_to_word or extract_pages_from_pdf. It also names the exact PDF4me API endpoint, leaving no ambiguity about the operation.

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 implies usage (you can create images from PDF pages), but it does not explicitly state when to use this tool versus alternatives like convert_pdf_to_pdfa or extract_pages_from_pdf. No exclusions or alternative recommendations are given, so it remains at an 'implied usage' level.

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