pdf_to_zip

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. It mentions extracting pages and creating a ZIP but does not specify output image format, default file naming, whether the input PDF is modified, or any side effects. This lack of transparency leaves the agent guessing about important behaviors.

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, concise sentence that front-loads the core action. It contains no unnecessary words or filler, making it efficient and easy to parse.

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's simplicity and lack of annotations/output schema, the description covers the main purpose but omits useful details like the image format used, how files are named inside the ZIP, and the default output filename pattern. These gaps could lead to uncertainty for an agent, but the core conversion-to-ZIP behavior is clear.

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 input schema provides descriptions for both parameters (file path and output_name with default behavior), and schema coverage is 100%. The description adds no additional meaning beyond what the schema already offers, so a baseline score of 3 is appropriate.

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: extracting all pages as images and bundling them into a ZIP archive. This specific verb+resource phrasing distinguishes it from siblings like pdf_to_png or pdf_to_jpg, which produce images but not a ZIP bundle.

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 the tool should be used when a ZIP archive of page images is desired, but it does not explicitly state when to use it versus alternatives (e.g., pdf_to_png for single images). No exclusions or alternative tool names are mentioned, so guidance is only implicit.

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