build_spritesheet

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

No annotations are provided, so the description carries full burden. It discloses that columns=0 means horizontal layout and that metadata is written optionally, but does not discuss side effects like overwriting dst or image format restrictions.

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?

Description is extremely concise, with a single sentence for the main purpose followed by a bullet-like list of arguments. No redundant words, front-loaded with the key action.

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?

Given no output schema and 5 parameters, the description covers all parameters and main behavior. Missing details on error handling, supported image formats, or performance implications, but sufficient for a straightforward packing tool.

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%, but the description adds clear meaning for all 5 parameters: frames (list ordered), dst (output path), columns (grid columns), cell_padding (inner padding), write_metadata (save JSON). It compensates fully for the schema gap.

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?

Description clearly states the tool packs multiple frames into a uniform grid spritesheet with JSON metadata. It uses specific verbs ('pack') and resources ('spritesheet'), and distinguishes from sibling tools like animate or autocrop.

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 mentions it's for engine importing but does not explicitly state when to use this tool versus alternatives like animate or pixelize. No guidance on prerequisites or exclusions.

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