pdf_to_jpg

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the core conversion. It does not mention output file naming, handling of multiple pages, whether the output directory is created, or any side effects.

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 with no filler, directly stating the tool's function. It is front-loaded and every word earns its place.

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 should explain what the tool returns (e.g., paths to generated files) and clarify behavior for parameters like 'pages'. The current description is too thin for an agent to invoke the tool confidently without further assumptions.

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?

All four parameters (dpi, file, pages, output_dir) have clear descriptions in the schema, so the tool description adds no additional meaning beyond reinforcing the overall purpose. The schema already covers the semantics adequately.

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 'Render PDF pages as JPEG images' uses a specific verb ('render') and explicitly names both the input (PDF pages) and output (JPEG images), clearly distinguishing it from sibling tools like pdf_to_png and pdf_to_tiff.

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 such as pdf_to_png or pdf_to_tiff. It only states the conversion without any context, exclusions, or preferences.

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