extract_pdf_images

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It explains input/output but omits important traits such as how it handles corrupted PDFs, permissions required, or whether images from headers/footers are included. Edge cases are not addressed.

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 well-structured with clear 'Args' and 'Returns' sections, and each sentence serves a purpose. It is concise enough, though the Returns section could be slightly more compact without losing clarity.

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?

The description covers input parameters and return values adequately for a tool with 4 params and no output schema. However, it lacks context about error handling, performance implications, or how it compares with siblings. Given the complexity of PDFs, more details on unsupported cases would improve completeness.

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?

With 0% schema description coverage, the description adds significant meaning by explaining each parameter's purpose, defaults, and filtering behavior. However, the format for the 'pages' parameter (e.g., '1-5,7') is not specified, leaving some ambiguity. Overall, it partially compensates for the missing schema descriptions.

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 extracts embedded images from PDF files, using the verb 'extract' and specifying the resource 'PDF images'. It distinguishes well from sibling tools like 'read_pdf_as_images' (which converts pages to images) and 'extract_pdf_tables' (extracts tables).

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 does not provide explicit guidance on when to use this tool versus alternatives. For instance, it does not mention that for extracting images from the entire page as rendered, 'read_pdf_as_images' should be used instead, nor does it specify prerequisites or limitations.

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