Palette Export Impl

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

No annotations are provided, so the description carries the full behavioral burden. It briefly characterizes one format's output ("paste-ready color-system context for any LLM"), but says nothing about the operation being a safe read, permissions, or how the export is produced.

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?

A single front-loaded sentence with no wasted words; the format enumeration is dense but appropriate. It reads as a value list more than a structured definition, but it is efficient.

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?

An output schema exists, so return values need no explanation, and the format options are covered. What is missing for correct invocation is the meaning/format of the required `palette` argument and any sense of when to choose this tool.

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 is 0% and the schema declares no enum, so the description's enumeration of the five fmt values (css, tailwind, json, svg, w3c, context) is the only documentation for that parameter and adds real value. However the required `palette` parameter is completely unexplained — its expected form (name, JSON, reference) is unknown.

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?

States a specific verb+resource ("Export tokens") and enumerates the output formats, which is enough to distinguish it from the sibling analyze/visualize/match tools. It does not explicitly name an alternative, but the export function is clear.

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 format list implies the agent picks a target format, but there is no explicit when-to-use guidance, no prerequisites, and no mention of when to prefer this over the twelve palette_* siblings. Usage is left to inference.

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