remove_palette_color

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

With no annotations provided, the description carries the full burden. It discloses key behaviors (remapping pixels, index shifting) but omits details like required permissions, reversibility, or side effects on other elements.

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 with no redundant words. The core action and key behavioral nuance (index shift) are front-loaded.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not mention return values, error cases (e.g., index out of bounds), or prerequisites like palette size constraints.

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 adds significant meaning beyond the schema: it explains that `remap_to` is where existing pixels go and that higher indices shift down. The schema covers 100% of parameters with descriptions, but the description ties them together operationally.

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 clearly states the verb 'Delete' and resource 'palette entry', and specifies the remapping behavior and index shifting. This distinguishes it from sibling tools like `set_palette_color` or `swap_palette_indices`.

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 description only implicitly states when to use (delete a palette entry) but provides no explicit guidance on when not to use it, prerequisites, or alternative tools (e.g., `replace_color` or `adjust_palette_color`).

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