ase_set_frame_duration_allSets the duration of every frame in an Aseprite sprite to a specified millisecond value, enabling uniform timing adjustments across animations.
Set every frame's duration in ms (unit-probed for Aseprite 1.3+).
| Name | Required | Description | Default |
|---|---|---|---|
| duration_ms | Yes | ||
| sprite_path | Yes |
| 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 exist, so the description carries the transparency burden. It does disclose the core behavior (overwriting every frame's duration with the given ms value) and adds a version-specific detail ('unit-probed for Aseprite 1.3+'). It does not mention permissions, reversibility, or side effects, but the primary behavioral effect is clearly stated.
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. The parenthetical about Aseprite 1.3+ is compact and adds version-relevant behavior, though it is slightly cryptic and could be clearer.
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-parameter mutation tool with an output schema, the description covers the essential operation and target scope. It lacks explicit guidance on prerequisites, single-frame alternatives, or behavioral caveats, but the tool is simple enough that the provided text is nearly sufficient.
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 add meaning. It clarifies that duration_ms is in milliseconds and applies to every frame, and sprite_path is implied as the target sprite file. It does not elaborate on ranges or constraints, but for two simple parameters the provided meaning is sufficient.
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 opens with a specific verb and object ('Set every frame's duration') and unambiguously states the unit ('ms'). It differentiates from the sibling ase_set_frame_duration by emphasizing 'every frame', so an agent can tell scope apart immediately.
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 word 'every frame' implies this is the tool to use when all frame durations should be changed uniformly, and it indirectly contrasts with ase_set_frame_duration. However, it never explicitly says 'use this for all frames, use ase_set_frame_duration for a single frame', leaving the when-to-use guidance implied rather than explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.