pixel_apply_palette

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

Discloses RGB distance matching, alpha preservation, transparent pixels untouched, and return format. Annotations already provide idempotent and destructive hints; description adds useful details about pixel handling and failure response.

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 wasted words. Front-loads purpose, then details behavior and return value. Efficient and structured.

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?

Despite no output schema, the description fully explains return format (JSON with fields and error case). Covers purpose, behavior, parameters, and return value comprehensively.

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?

Input schema provides descriptions for all parameters; description adds value by mentioning preview returns a rendered image. The description does not repeat schema details but complements them.

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?

Cleary states the tool snaps opaque pixels to nearest color in a palette, with specific verb 'snap' and resource 'every opaque pixel'. Distinguishes from siblings like pixel_replace_color and pixel_flood_fill by describing a unique use case: enforcing a consistent game palette.

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?

Implicitly indicates when to use (enforce consistent palette, clean up stray colors) without explicit exclusions or alternative tool names. Provides clear context of usage from the description.

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