list_palette_presets

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

With no annotations, the description carries the disclosure burden; the verb 'List' communicates a read-only operation with no mutation or argument side effects. It does not say what exactly is returned (names, color maps, metadata), but for this zero-parameter tool the core behavior is transparent.

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?

The description is a single front-loaded sentence with no filler, and every word ('built-in', 'retro') contributes meaning. It is appropriately sized for a zero-parameter list operation.

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 tool with no parameters, no output schema, and no annotations, the description states the action and scope sufficiently for an agent to invoke it. It would be slightly stronger if it mentioned that the returned preset names are reusable with apply_palette_preset, but that is not required for basic invocation.

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 input schema is empty (0 parameters), so the baseline is 4; there are no parameters for the description to clarify. It still adds value by specifying that the items being listed are built-in retro presets rather than user-defined palettes.

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 uses a specific verb ('List') and an explicit resource ('built-in retro palette presets'), and the qualifiers 'built-in' and 'retro' separate this from general palette inspection or apply tools. It does more than restate the tool name, so an agent can tell what is being listed.

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?

It gives no explicit when/when-not guidance and names no alternative tool, so an agent must infer that listing is the right action when it needs available built-in retro presets. The intended use is implied by the verb and noun but not contrasted with siblings such as apply_palette_preset or get_palette.

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