Run Aseprite Command Sequence

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the transparency burden. It discloses key side effects: opening input files and saving the active sprite. However, it does not mention potential mutation of sprites in memory, failure behavior when commands are disabled, or the fact that it runs headless via batch mode (though the schema covers batch). This is adequate but not rich.

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, efficient sentence that front-loads the core purpose and mentions the two most important optional side effects (opening and saving). No wasted words; every phrase earns its place.

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 tool with 11 parameters and no output schema, the description plus the high-coverage schema provide enough context to understand the tool. The main missing piece is a high-level overview of the command sequence flow (e.g., actions are applied sequentially), but the schema's `actions` array structure implies this. Overall, the purpose and key behaviors are sufficiently covered.

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 91%, so the baseline is 3. The description does not add parameter-level detail beyond implying inputFiles and saveAs, but the schema already provides thorough descriptions for all parameters. No extra value is needed or provided.

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 uses a specific verb ('Run') and identifies the exact resource ('Aseprite app.command.<CommandId>(params) actions through Lua'), with clear scope (optionally opening files and saving the active sprite). It distinguishes itself from sibling tools like aseprite_run_lua and aseprite_cli by focusing on the app.command command sequence mechanism.

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 explicit guidance is provided about when to use this tool versus alternatives such as aseprite_run_lua or aseprite_cli. The description only states what the tool does, leaving the agent to infer appropriate usage from the name and schema.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.