harmony_generate_palette

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

No annotations, so the description carries the burden. It discloses real behavioral content — that the scheme choice determines how secondary/accent hues are derived and the character of each option — but says nothing about determinism, whether output is tokens or raw hex, or how multiple input colors interact. Return behavior is entirely undisclosed and no output schema exists.

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?

Front-loaded with the outcome, then a tight bulleted list that earns its space by disambiguating the non-obvious enum. Slight redundancy: color_scheme is described both at top level and inside preferences, and its enum values are repeated in the schema.

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?

Given a generation tool with no annotations and no output schema, the description covers inputs well but leaves the return value opaque — an agent cannot tell whether it receives hex ramps, design tokens, or a theme object. The nested preferences object is only lightly explained.

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 100%, so baseline is 3, but the description goes beyond the schema by explaining what each color_scheme enum value actually produces (elegant/unified, calm/cohesive, high contrast, balanced, nuanced). The other parameters (corners, density, type_style, etc.) get no added meaning in the description.

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?

Opens with a specific verb (generate) and resource (working color system) and enumerates exactly what ships: primary/secondary/accent ramps, neutrals, semantic colors. Combined with the sibling set (fonts, scale, shadows, motion), an agent can tell this is the palette tool without opening the schema.

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?

No explicit when-to-use/when-not and no named alternative among siblings. The one piece of guidance, that preferences should be passed identically to every tool for cross-tool consistency, is useful workflow context but not routing advice.

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