export_sprite

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

With no annotations, the description carries the full burden, and it does add some transparency by noting that the tool confirms Aseprite wrote the output file. However, it does not disclose side effects such as overwriting existing files, required permissions, directory creation, or error behavior when the output is not written.

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 concise sentence that front-loads the core operation. It avoids irrelevant detail, though the phrase 'confirm that Aseprite wrote an output file' could be slightly tighter without losing meaning.

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 a side effect, no annotations, and no output schema, the description is too thin. It does not explain the return value, failure modes, overwrite behavior, or file path semantics, leaving gaps that an agent would need to guess at.

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 hints at 'sprite' (filename), 'output file' (output_filename), and 'image format' (format), but it never maps these concepts to the actual parameter names or explains their expected values beyond what the schema already provides.

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, specific action: export a sprite to an image format and verify Aseprite wrote an output file. It references the resource 'sprite' and the 'selected image format', but it does not explicitly differentiate itself from sibling export tools like export_frame, export_layers, export_tag, or export_spritesheet.

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?

There is no guidance on when to choose this tool over sibling export tools. Since many siblings perform related exports, the description leaves the decision to the agent's inference rather than stating explicit use conditions or alternatives.

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