pdf_to_jpg

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

Discloses return format (zip archive) and mode behavior, but lacks details on nondestructive nature, auth requirements, or error handling. Adequate for a straightforward conversion tool without annotations.

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 sentences, no fluff. Front-loaded with main purpose; each sentence adds essential information.

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?

Covers core behavior, parameters, and return format. Without an output schema, the description adequately describes output. No missing critical details for this low-complexity 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 100%, but description adds minimal extra context beyond the schema (e.g., zip archive output). No detailed parameter constraints or examples provided.

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 action ('Convert a PDF to JPG images') and specifies the two modes ('pages' and 'extract'), which distinguishes it from sibling tools like pdf_to_word or extract_pdf_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?

No guidance on when to use this tool over alternatives (e.g., when to use 'extract' mode vs. extract_pdf_pages). No exclusions or context for choosing among siblings.

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