Generate Heritage Palette from Cultural Concept

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

Annotations provide readOnlyHint. Description adds that colors are sourced from archive with documented history, which is useful. No mention of performance or limits, but sufficient for a generation 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 sentences, front-loaded with purpose, then examples, then sourcing detail. No wasted words, highly scannable.

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 output schema exists (implied by 'hex values, proportions, provenance') and parameter coverage, description is fairly complete. Lacks differentiation from `palette_heritage`, but minor.

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 covers all parameters with good descriptions. Description reinforces with concrete examples for `concept`, adding value beyond schema.

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?

Description clearly states verb (Generate), resource (colour palette), and context (from cultural concept). Examples further clarify. Distinguishes from siblings like `palette_generate` by specifying historical grounding.

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?

Examples give clear usage context, but no explicit guidance on when to use this vs. `palette_heritage` or other palette tools. However, the concept-based nature is implied.

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