Export any animation frame to a PNG file with nearest-neighbor integer scaling. Specify frame index, scale, and filenames to produce the output image.
Export one animation frame as a PNG with nearest-neighbor integer scaling.
| Name | Required | Description | Default |
|---|---|---|---|
| scale | No | ||
| filename | Yes | ||
| frame_index | Yes | ||
| output_filename | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions nearest-neighbor integer scaling, which is useful, but doesn't disclose whether the operation is read-only or mutating, whether it writes to disk, what happens if the file exists, or any side effects. For an export tool, this is a significant gap.
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 concise sentence that front-loads the core purpose. It's efficient and doesn't waste words, though it could add a bit more detail without becoming bloated.
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 has 4 parameters, no output schema, and no annotations, the description is too sparse. An agent needs to know what 'filename' refers to (input sprite?), what 'frame_index' means (0-based or 1-based?), and what 'output_filename' should be. The description doesn't explain the relationship between these parameters or the expected output format beyond 'PNG'.
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 the schema's lack of parameter documentation. The description mentions 'nearest-neighbor integer scaling' which relates to the 'scale' parameter, but doesn't explain the meaning of 'filename', 'frame_index', or 'output_filename' beyond what their names imply. It doesn't clarify the relationship between input and output filenames or the frame indexing convention.
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 specific verb and resource: 'Export one animation frame as a PNG with nearest-neighbor integer scaling.' This clearly identifies the tool's function and distinguishes it from sibling export tools like export_animation_gif or export_spritesheet, though it doesn't explicitly name them.
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 usage context (exporting a single frame as PNG with integer scaling) but provides no explicit guidance on when to choose this over alternatives like export_animation_gif or export_spritesheet. The sibling list contains many export-related tools, and the description doesn't differentiate them.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.