Adjust the active sprite's canvas dimensions to a new width and height with anchor placement, avoiding interpolation or blurring.
Resizes the active sprite canvas dimensions without interpolation or blurring.
| Name | Required | Description | Default |
|---|---|---|---|
| width | Yes | New canvas width | |
| anchor | No | Anchor point for resizing | top_left |
| height | Yes | New canvas height |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It mentions no interpolation or blurring, which is useful, but omits whether existing pixel content is preserved, cropped, or repositioned, whether the operation is reversible, and what permissions or context are required.
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?
A single sentence that is front-loaded and wastes no words, though it is very short and could benefit from slightly more context without becoming verbose.
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 mutation tool with no annotations, no output schema, and only 3 parameters, the description is too thin. It should clarify what happens to existing content (preservation, cropping, padding) and whether undo is supported.
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%, so the schema already documents width, height, and anchor including enum values and a default. The description adds no parameter-level detail beyond the schema, making the baseline 3 appropriate.
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?
States a specific verb and resource ('Resizes the active sprite canvas dimensions') and clearly distinguishes from pixel-drawing siblings by noting it does not interpolate or blur. It does not, however, name or differentiate from a sibling like create_frame or set_pixels explicitly.
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 on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description simply states what it does.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.