extract_pdf_images

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

The description mentions pagination and return type (list of image contents and summary), but does not elaborate on what 'image contents' means (e.g., format, encoding) or disclose potential side-effects. Since there are no annotations, the description could provide more behavioral context, but it is not misleading.

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 extremely concise: three sentences with zero wasted words. The most important information (action, pagination, batch recommendation, return type) is front-loaded and clearly ordered.

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 low complexity (simple extraction with 3 parameters and a basic output schema), the description covers the essential aspects: what it does, how to paginate, and what is returned. It could mention file limitations or format details, but it is otherwise complete for an agent to use correctly.

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 three parameters are fully described in the schema (100% coverage), so the baseline is 3. The description adds value by explaining the recommendation for batch size (max_images) and pagination context (start_index), which clarifies usage beyond the schema.

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: 'Extract images from a PDF file with pagination.' The verb 'Extract' and resource 'PDF file' are specific, and the mention of pagination distinguishes this from a simple one-shot extraction. With no sibling tools, this is a strong purpose statement.

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 explicit usage advice: 'Works best when extracting small batches of images (e.g., 10) at a time.' This guides the agent on batch size. It does not mention when not to use or alternatives, but with no siblings, the guidance is sufficient.

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