delete_custom_palette

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

No annotations are provided, so the description carries the full burden, yet it never states whether deletion is permanent or reversible, what happens to palettes referenced by designs, or what the tool returns. The 'Requires Kiln Pro' line hints at an entitlement gate, but it reads as an upsell rather than a behavioral disclosure, and the remaining three lines of pricing copy add noise rather than transparency.

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 useful content is one short sentence; the following three lines are a feature blurb and a pricing URL that do nothing for tool selection or invocation. Front-loading is fine, but roughly 75% of the text does not earn its place.

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?

This is a destructive mutation with no annotations, no output schema, and an undocumented parameter, so the description must supply safety and behavior context. Instead it omits irreversibility, error behavior, and entitlement details while spending most of its length on unrelated Pro-tier advertising.

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 schema has a single required parameter 'name' with 0% description coverage, so the description needed to clarify that this is the palette's display name, whether matching is case-sensitive, or what happens on an unknown name. It says nothing about parameters at all, leaving the sole input entirely undocumented.

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 first sentence gives a specific verb+resource ('Delete a saved custom color palette'), which is unambiguous and clearly distinct from siblings like save_custom_palette and list_custom_palettes. It stops short of explicitly naming those siblings as alternatives, so it lands just below a 5.

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?

There is no guidance on when to use this versus alternatives, nor any preconditions such as whether the palette must exist or be unlocked. The only conditional signal ('Requires Kiln Pro') is buried in marketing copy rather than framed as a usage requirement.

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