Flatten a sprite and export it as a PNG file. Provide the sprite path and output PNG path to generate the image.
Flatten and export a sprite to a PNG file.
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | ||
| out_path | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must fully disclose behavior, but it only says 'flatten and export.' It does not state whether flattening modifies the original sprite, whether an existing PNG file is overwritten, or what happens to unsupported sprite features.
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. It is appropriately concise, though the brevity comes at the cost of important behavioral detail.
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 two-required-parameter tool with no annotations and zero schema description coverage, this one-liner leaves critical gaps such as overwrite behavior, path requirements, and whether flattening is destructive. The output schema may cover return values, but it does not compensate for the missing operational context.
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%, and the description only loosely maps 'path' to the sprite and 'out_path' to the PNG destination. It adds no detail about accepted path formats, required extensions, or the relationship between the two parameters.
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 action—flatten and export a sprite to a PNG file—and names the resource and output format. 'Flatten' adds behavioral differentiation from simpler data-returning tools like get_png_data, though it does not explicitly contrast with siblings.
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?
No guidance is given about when to use this tool versus alternatives such as get_png_data or create_sprite. The description implies the intended use but provides no context, prerequisites, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.