export_layers

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

Discloses that output_directory is created if missing and include_hidden defaults to False. Lacks details on error handling, file format requirements, or any side effects.

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?

Extremely concise, front-loaded with the main purpose, and uses a clean Args structure. Every sentence adds value.

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?

Covers key parameters and basic behavior. Lacks details on return values or error handling, but sufficient for a straightforward export tool given no output schema or annotations.

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 has 0% description coverage, but the description adds meaningful context for all three parameters (filename as Aseprite file, output_directory auto-creation, include_hidden default). Compensates well for missing schema descriptions.

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?

Clearly states the tool exports each layer as a separate PNG file with a specific naming convention. This distinguishes it from sibling tools like export_sprite 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?

Implies usage for exporting layers individually, but does not provide explicit when-to-use guidance or compare with alternatives like export_spritesheet.

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