save_sprite

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

Annotations only declare it is a non-read-only, non-destructive write; the description adds real behavior beyond that — copy preserves the file name, the extension determines format, single-image formats emit one file per frame, and the result enumerates written files. It does not say what happens on overwrite, which is the one notable gap.

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?

Three compact sentences, all front-loaded with the primary action first and the copy exception immediately after. No filler, though the frame-naming example is slightly more detail than most callers need.

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?

With no output schema, the description compensates by stating that the result lists the files written, and it covers the copy/format branching. It is nearly complete for a mutation tool, missing only overwrite/permission semantics.

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 50%, and the description usefully defines the undocumented copy parameter's semantics. However, file and backend behavior is left to the schema (backend has its own description) and the description adds no format/syntax detail for the file path beyond what is already structured.

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?

States a specific verb and resource ('Saves a sprite') and distinguishes the three modes (Save, Save As, copy=true). It does not differentiate itself from nearby siblings like export or export_sprite_sheet, so an agent still has to infer which write-path applies.

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?

It explains the copy=true condition, which is genuinely useful routing, but gives no guidance on when to save vs. use export/export_sprite_sheet, and no prerequisites such as whether a file must already exist for Save.

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