apply_palette_preset

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

With no annotations, description carries full burden. States it only sets palette without modifying pixels and hints at post-processing. Lacks details on whether palette is replaced or merged, and no mention of reversibility or side effects. Adequate but not rich.

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 concise sentences followed by Args section. Front-loaded with core action and context. Every sentence adds value; no wasted words.

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?

Covers core behavior, distinguishes from sibling, suggests follow-up tool. Lacks error handling or format constraints, but for a simple two-param tool without output schema, it is largely complete.

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 0%, so description must compensate. Lists example presets for 'preset' parameter, adding value beyond schema titles. However, does not specify format or full list, though sibling list_palette_presets exists. Minimal additional meaning for 'filename'.

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?

Clear verb 'Set' with specific resource 'sprite palette'. Explicitly states it applies 'built-in retro presets', distinguishing it from sibling tools like set_palette (which likely allows arbitrary palettes) and quantize_to_palette (which snaps pixels).

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?

Provides explicit context: 'only sets the palette; existing pixels keep their colors' and suggests using quantize_to_palette afterwards. Implicitly distinguishes from set_palette by focusing on presets. No explicit when-not-to-use but sufficient for this tool.

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