extract_palette

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

With no annotations, the description carries the burden, and it does disclose one important behavior: the tool returns an image and the color extraction is done by the agent, not server-side. However, it says nothing about the image payload format, whether `count` constrains anything given visual extraction, or what happens if the reference is missing — significant gaps for a mutation-adjacent analysis tool.

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?

Two short sentences, front-loaded with the return behavior. Slight waste in the vague phrase "with guidelines for identifying dominant colors," which is never elaborated.

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?

A 4-parameter tool with no annotations and no output schema needs the description to explain what comes back and how `count` interacts with the visual-extraction workflow; neither is addressed. The return-format gap is the most consequential omission.

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 100%, so all four parameters (referenceId, count, seriesId, sketchId) are already documented in the schema. The description adds no syntax, defaults, or parameter meaning beyond that, so the baseline of 3 applies.

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?

It states a specific action — return a reference image so the palette can be read off it — but this conflicts with the tool name, which implies the palette is computed and returned. The description never distinguishes this from nearby tools like analyze_reference or design_get_style_palette, so an agent may pick the wrong one.

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 agent extracts hex colors visually" hints at the workflow, but there is no explicit when-to-use, when-not-to-use, or named alternative among the many palette/reference siblings. The agent must infer the routing decision.

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