Add a deterministic count of animation frames to an existing Aseprite file, with optional per-frame duration in milliseconds. Specify the exact frame count to control animation length and sequencing.
Add a deterministic number of animation frames.
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| filename | Yes | ||
| duration_ms | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of disclosure. It only says 'add a deterministic number of animation frames,' leaving unclear whether frames are appended or inserted, what 'deterministic' means regarding frame counts, and any side effects on existing animation data. This is severely under-disclosed.
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 sentence, which is concise, but it is too lean to be useful. It does not front-load any key distinctions or constraints. A sentence that adds little information is not efficient – it is merely brief.
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 absence of annotations, output schema, and rich parameter documentation, this description is grossly incomplete. It does not explain the relationship to sibling tools, the meaning of 'deterministic,' or expected behavior. An agent has almost no basis to call this tool correctly.
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 explain parameter meaning, but it mentions none of the three parameters (filename, count, duration_ms). An agent cannot infer what 'count' refers to or what duration_ms does from the description alone.
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 ('Add') and resource ('animation frames'), indicating the core operation. However, it does not differentiate from sibling tools like 'add_frame' or clarify whether multiple frames are added at once. The term 'deterministic' adds ambiguity, but the basic purpose is discernible.
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 provided on when to use this tool versus alternatives such as add_frame, copy_frame, or propagate_frame_to_range. There is no mention of prerequisites, typical use cases, or scenarios where this tool is inappropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.