art.aseprite.export

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

With no annotations, the description must disclose behavior, and it does add a key fact: the tool saves a canvas as PNG and returns a CLI command for external execution rather than performing the conversion itself. However, it does not describe side effects (where the PNG is saved, whether the session is modified), prerequisites, or failure modes, leaving significant behavioral gaps.

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 short with no wasted words and front-loads the export purpose before the mechanism. The first and second sentences are slightly redundant in saying Aseprite conversion twice, but overall the structure is efficient.

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?

There is no output schema, yet the description only says commands are returned without stating their format or how the agent should execute them. Given that external execution is the core behavior, an agent needs more detail about the returned command structure and expected follow-up actions.

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 coverage is 100%, so session_id and output_name are already documented in the input schema. The description adds no additional meaning about these parameters, which is acceptable but means it earns only the baseline score.

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 names a concrete action and resource: exporting a canvas session to Aseprite format, and it clarifies the mechanism (saving PNG and producing an Aseprite CLI command). This makes it distinguishable from the other art.aseprite.* siblings (validate, spritesheet, layers). There is minor ambiguity because the first sentence implies a direct .aseprite export while the following sentence reveals the tool only returns a conversion command.

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 description does not say when to choose this tool over art.aseprite.spritesheet, art.aseprite.layers, or the many asset/canvas export tools. It only implies usage via the purpose statement and the note that commands are returned for external execution, which is not enough guidance for an agent choosing among siblings.

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