extract_images

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

No annotations are provided, so the description carries the full burden. It states the core behavior but does not disclose what happens with output_dir (whether it is created, default location if omitted), what format or naming scheme the extracted images use, or whether the action is reversible. This lack of behavioral context leaves the agent uncertain about 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 one concise, clear sentence without unnecessary words. It captures the tool's purpose efficiently and earns its place than extended prose.

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 tool is simple with two parameters and no output schema. However, the description omits behavior around the optional output_dir (whether it is created, default behavior) and does not mention return values or file naming. Given the low complexity, the description is adequate but has notable gaps that could confuse an agent.

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%, with both parameters documented. The description adds no additional meaning beyond the schema, so the baseline score of 3 is appropriate. No new parameter semantics are introduced.

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 purpose: extracting all embedded images from a PDF. It uses a specific verb ('extract') and resource ('PDF'), and distinguishes itself from sibling tools like pdf_to_png or pdf_to_jpg, which convert pages rather than extracting embedded images.

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 embedded images need to be extracted, but it does not explicitly mention when not to use it or provide alternative tools. No distinction is made from similar extraction tools like extract_attachments, so only implied usage guidance is present.

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