Auto-beautify

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

With no annotations, the description carries the full behavioral burden. It is silent on whether pixels are modified in place, whether the operation is reversible/undoable, how scope resolves (allFrames defaults true per schema, but the description never mentions it), and what happens if all effect flags are false. Only the visual transforms themselves are disclosed.

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 front-loaded sentence packs the effect list efficiently and the example is compact and demonstrates a working call. Minor cost: the effect list is dense prose that could be a terser enumeration, but little is wasted.

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 no annotations and no output schema, the description should state scope semantics (allFrames default true), defaults for the effect booleans, and whether changes are destructive. None of that is covered, leaving the agent under-informed before a state-changing call.

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?

The description maps to several parameters (outline, shade, despeckle, limitColors, symmetry, center) and the example supplies concrete values and ranges (limitColors:16, upper bound 64 in schema). However, with 38% coverage, seven parameters — crop, frame, layer, project, allFrames, light, harmonize — get no meaning from either schema or description, and 'light'/'harmonize' are the least self-explanatory.

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 names concrete operations (despeckle, palette limiting, outline, hue-shifted shading, symmetry/centering) so an agent knows this is a batch beautification pass on sprite pixels. It is clear but never states the tool's verb/resource explicitly (e.g. 'modifies the active frame's layer') and doesn't distinguish itself from siblings like sprite_draw_ops or sprite_generate.

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?

There is no guidance on when to reach for this versus sprite_generate, sprite_draw_ops, or sprite_critique, nor when not to. 'One-click pro polish' implies a finishing step but the agent must infer that, and no prerequisites or preconditions are given.

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