extract_files

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

No annotations are provided, so the description carries the full behavioral burden. It says files are saved to a folder but does not disclose overwrite behavior, directory creation, permissions, failure modes, or whether the operation is destructive to existing files.

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 definition is a single, front-loaded sentence with no wasted words. It states the core action and scope immediately.

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?

Although an output schema exists, the description leaves critical input semantics undocumented: what path refers to and how out_dir defaults when null. For a file-writing tool with no annotations and 0% schema description coverage, this is incomplete for reliable invocation.

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 for both parameters. It only vaguely implies an output folder via 'to a folder' and says nothing specific about the required path parameter or what happens when out_dir is null.

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 uses a specific verb and resource: save embedded PDFs and images (backgrounds, pasted pictures) to a folder. It is clearer than the generic tool name extract_files, but it does not distinguish this from sibling tools like export_pdf or output_folder that also write files.

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 only implied usage cue is that the tool handles embedded PDFs and images, but there is no explicit guidance on when to use this instead of export_pdf, render_page, or output_folder. No prerequisites or exclusions are stated.

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