set_sprite_properties

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

Annotations declare a non-read-only, non-destructive write, and the description confirms mutation of metadata with a list of targets. However, it does not disclose persistence/save semantics, undo behavior, or batch vs live implications; those details appear only in some schema properties.

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?

A single sentence, front-loaded with the verb, followed by a compact list. There is no filler or restatement of annotations.

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 13-parameter mutation tool with nested object parameters and no output schema, the description covers the metadata targets but leaves operational context thin: it does not explain save defaults, backend selection, or how to target a sprite. The schema fills some gaps, but several parameters (useLayerUuids, data, colorSpace) lack explanatory text in either place.

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 46%, so the description should compensate. It maps several parameters to human-readable concepts (filename, tab color, transparent color index, pixel ratio, grid bounds, user properties, color space), but omits save, sprite, backend, useLayerUuids, and convertColorSpace, and gives no format details beyond the 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?

States a specific verb 'Changes' and resource 'sprite metadata', then enumerates eight metadata fields (filename, user data, tab color, transparent color index, pixel ratio, grid bounds, user properties, color space). This distinguishes it from layer/frame/cel tools, but it does not name a sibling alternative or clarify overlap with the generic 'properties' tool.

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 when-to-use, when-not-to-use, or alternative guidance is provided. It does not explain when to choose this over update_layer, properties, or change_color_mode, nor does it mention prerequisites like an open sprite or backend choice.

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