export_spritesheet

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

With no annotations, the description carries full burden but fails to disclose behavioral traits like file overwriting behavior, required permissions, or side effects. While parameter meanings are detailed, the actual operation (e.g., does it overwrite existing file?) is not addressed.

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 well-structured with a clear initial sentence followed by a list of parameter descriptions. It is concise and each line adds value, though some default values are repeated from the schema.

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?

The parameter details are thorough, but the description lacks explanation of the output format (e.g., JSON structure), behavior on existing files, and the exact effect of flags like list_tags. Given no output schema, more context on the result would improve completeness.

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 fully compensates by explaining each parameter's meaning, default behavior, and allowed values (e.g., sheet_type options, data_format options, scale/padding units). This adds essential context beyond the bare schema.

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 clearly states 'Export frames as a sprite sheet' with optional JSON data file, using a specific verb and resource. It distinguishes from sibling tools like export_frame (single frame) and export_sprite (whole sprite) by the output format.

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 guidance is provided on when to use this tool over alternatives like export_frame or export_layers. The description lacks context such as prerequisites, when to prefer spritesheet export, or when the JSON data file is beneficial.

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