palette_edit

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds genuinely useful behavior context beyond that — indexed-sprite pixels are remapped to preserve their colors, and pixels whose colors are removed fall back to the nearest remaining entry. It still omits whether the palette is persisted by default or how failures surface, but the remap semantics are substantial added value.

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 sentences, front-loaded with the core verb and the full action inventory, then the side-effect caveat. The long parenthetical sort-key list is bulky but each operation enumerated is load-bearing for action selection.

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?

A 17-parameter mutation tool with no output schema, so the description carries more burden than it does. It covers the action space and the key side effect well, but says nothing about return shape, save/persistence defaults, or error behavior, which leaves gaps an agent must guess at.

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 71% and the schema already documents most parameters including per-action applicability. The description contributes the sort key list (matching the 'by' enum), the remapPixels side effect, and the action vocabulary, but leaves many of the 17 parameters (save, backend, steps, insert, sprite, descending) solely to schema text.

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 (Edits) and resource (palette structure) and enumerates the eight discrete operations, so an agent immediately knows the action space. It does not, however, distinguish itself from adjacent palette siblings like set_palette, get_palette, or save_palette, leaving that routing inference to the reader.

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?

Usage is only implied through the action list and one parameter-level hint ('set remapPixels=false to skip'). There is no explicit when-to-use guidance, no statement of when to prefer set_palette/replace_color instead, and no stated prerequisites for choosing between live and batch backends beyond what the schema says.

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