pdf-to-jpg

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. However, it only restates the core action without detailing output behavior (e.g., file creation, multiple images), potential side effects, authentication needs, or limitations. It adds no meaningful behavioral context beyond the tool name itself.

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, front-loaded sentence that efficiently states the tool's purpose. It is appropriately sized for a tool with a self-explanatory name, though given the tool's parameter complexity (5 params including modes), a bit more context would improve it without becoming verbose.

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 and five parameters, the description is incomplete as it does not explain return values (e.g., output file paths), the difference between 'pages' and 'extract' modes, or default behavior for output directory and filename. The schema covers parameters but not the tool's overall behavior or result format, leaving significant gaps for an agent.

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%, with all five parameters having clear descriptions (e.g., dpi, file, mode, outputDir, outputFilename). The description itself adds no additional parameter semantics, so the baseline of 3 applies as 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 clearly states the tool's function: converting PDF pages to JPG images. It uses a specific verb (convert) and resource (PDF pages), and the result (JPG images) is unambiguous. This distinguishes it from sibling tools like images-to-pdf, which performs the reverse 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 provides no explicit guidance on when to use this tool versus alternatives. It implies usage through its clear purpose, but it lacks statements about when not to use it or how it compares to other PDF tools. No exclusions or alternative tool names are mentioned.

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