ase_create_canvasCreates a new Aseprite sprite with specified dimensions, color mode (RGB, grayscale, or indexed), and optional output path, returning the file path.
Create a new .aseprite sprite (rgb|grayscale|indexed). Returns its path.
| Name | Required | Description | Default |
|---|---|---|---|
| width | Yes | ||
| height | Yes | ||
| out_path | No | ||
| color_mode | No | rgb |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 full behavioral burden. It discloses that a new sprite is created and its path is returned, but doesn't state what happens to any current/active sprite, whether the file is written immediately, or overwrite behavior.
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 efficient sentence that front-loads the core purpose and includes the key color-mode detail plus return value. No wasted words, appropriately sized.
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 simple creation tool with an output schema, the description covers purpose, color modes, and return. But with 0% schema coverage, no annotations, and no explanation of out_path semantics or required dimensions, some gaps remain for correct 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. It explains color_mode options (rgb|grayscale|indexed) but says nothing about width, height, or the out_path parameter, including its null default and what null implies. Only partial compensation for the coverage gap.
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 'create' and resource '.aseprite sprite', and notes the supported color modes. The resource is clear enough to distinguish from export/save/color-mode tools, though it doesn't explicitly name which sibling it is not.
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 like ase_save_as or ase_color_mode. No context about prerequisites (e.g., whether an existing sprite is required) or when creation is appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.