Extract every frame as a PNG image from a .pclx animation file and write the images to a specified output directory.
Extract all frame PNG images from a .pclx file into a target directory.
| Name | Required | Description | Default |
|---|---|---|---|
| output_dir | Yes | Directory where extracted frame images will be written. | |
| project_path | Yes | Path to the .pclx file. |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral burden. It discloses that PNG files are written into the output directory, but omits important side-effect details such as overwrite behavior, whether the directory is created, file naming, and what happens on failure.
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 front-loaded sentence with no filler. Every part—verb, resource, source file, and destination—earns its place.
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 low-complexity, two-parameter extraction tool, the description covers the core action and destination, and the schema fully documents both parameters. However, without annotations or an output schema, the lack of behavioral detail around file writing leaves clear gaps.
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 100%, and the schema already documents both parameters with clear descriptions. The description reinforces the mapping but adds no extra syntax or constraints beyond what the schema provides, which fits the baseline of 3.
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 states a clear verb ('Extract') and specific resource ('all frame PNG images from a .pclx file') with the destination ('target directory'). It is understandable without the schema, but it does not explicitly distinguish this from sibling tools like pencil2d_export or pencil2d_create_spritesheet.
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 explicit when-to-use guidance, prerequisites, or alternatives. An agent must infer usage from the purpose alone, and there is no indication of when to prefer this over pencil2d_export or pencil2d_create_spritesheet.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.