new_sprite

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered. The description adds a genuinely useful batch-mode constraint (file required, sprite saved there), but says nothing about the live-vs-batch execution difference, failure modes, or state 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?

Two short sentences with zero filler, and the primary purpose is front-loaded before the conditional constraint. Nothing to trim.

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 an 11-parameter creation tool with 45% schema coverage and no output schema, the description is thin. It addresses only 'file' and leaves the agent to infer defaults, backend behavior, and the meaning of most creation options.

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 only 45%, so the description should compensate. It clarifies the batch-mode requirement for the 'file' parameter beyond the schema's 'Save to this path' note, but 9 other parameters (frames, colorMode, layerName, frameDurationMs, etc.) get no description-level help. Partial compensation only.

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 ('Creates a new sprite'), which is clearly distinct from sibling tools like open_sprite and duplicate_sprite. It does not explicitly name those alternatives, so it falls short of the top mark.

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 only contextual guidance is the batch-mode 'file' requirement. There is no indication of when to use this versus open_sprite (existing file) or duplicate_sprite, nor any prerequisites for the live backend.

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