Tool Extract Images

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

With no annotations, the description carries the burden of behavioral disclosure. It does usefully reveal that list_only=true returns a listing without writing files, implying the default behavior writes PNGs to disk. However, it does not disclose output location defaults, permission requirements, overwrite behavior, or what happens when no images are found.

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 compact sentence that front-loads the core action and then adds the important list_only variant. There is no filler or redundancy; every word contributes 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?

For a tool with four parameters, zero schema descriptions, and no annotations, the description is too thin. It explains list_only but leaves pages and out_dir unexplained and provides no usage guidance. The presence of an output schema helps, but the agent still lacks enough context to invoke the tool with non-default parameters confidently.

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 description coverage is 0%, so the description must compensate, but it only explains list_only. It does not clarify the meaning of pages, out_dir, or path, leaving key parameters undocumented. Some meaning for path is implicit via 'PDF,' but pages and out_dir remain opaque.

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 a specific action and resource: extracting embedded images from a PDF and saving them as PNG. It also mentions the list_only behavior, which helps distinguish it from sibling tools like tool_extract_text, tool_render_pages, and tool_extract_attachments.

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 gives no guidance about when to prefer this tool over alternatives, nor does it mention any exclusions or context where another sibling like tool_render_pages or tool_extract_attachments would be more appropriate. Usage context is only implied by the tool's name and the phrase 'embedded images.'

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