generate_palette

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds useful output context (palette is tonal HSL derived from a single seed, contrast pairs are 'actual opaque' rather than alpha approximations), but it says nothing about the dark/light mode's effect on output or determinism beyond what the idempotent hint implies.

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 that covers both the generation and the contrast-pair computation with no filler. Slightly opaque phrasing ('actual opaque contrast pairs') adds a touch of ambiguity without bloat.

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?

With no output schema, the description does describe the two outputs (palette and contrast pairs), which is valuable. However, for a tool whose only optional parameter is an unexplained dark/light mode, and which gives no hint of output shape or size, it is only minimally sufficient.

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 description coverage is 0%, so the description carries the burden. It conveys that a single seed color drives generation ('from one seed'), implicitly documenting the required 'seed' parameter, but the optional 'mode' enum (dark/light) is never mentioned and its effect is left unexplained.

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 and resource: generate a tonal HSL palette from one seed, plus a secondary computation of opaque contrast pairs. It is clearly distinguishable from siblings like analyze_contrast or generate_type_scale, though it does not name or contrast itself against those siblings.

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 description gives no when-to-use guidance, no exclusions, and never mentions alternatives such as analyze_contrast for standalone contrast checking or get_design_tokens for existing palettes. Usage must be inferred entirely from the verb and tool name.

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