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

Beyond the readOnlyHint annotation, the description adds valuable behavioral context: the result already includes rendered palette and downloads, the agent should show those to the customer, must not present archive anchors as the recommended colours, and should call palette_finalize once if choosing its own palette. These are meaningful, non-obvious behaviors that guide invocation.

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?

The description is dense but well-structured: the primary function is front-loaded, followed by output contents, customer-facing instructions, and a critical workflow rule. Each sentence earns its place and there is no redundant or filler content.

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 the output schema exists and annotations declare read-only behaviour, the description is complete for a tool of this complexity. It explains what the tool returns, how to handle the results, the key anti-pattern to avoid, and the downstream palette_finalize step when needed.

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?

The input schema already covers all three parameters with descriptions, so the baseline is 3. The description reinforces the 2-8 hex value constraint and mentions room/surface outputs, but it does not add much beyond the schema for style or room_type semantics.

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?

The description opens with a specific action and resource: generating a complete interior specification from 2-8 hex values. It further clarifies the tool's outputs (surface assignments, 60-30-10 proportions, lighting behaviour, archive colour names), which clearly distinguishes it from siblings like palette_finalize or palette_generate.

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 clearly implies when to use the tool (given 2-8 hex values to produce an interior specification) and gives an explicit conditional handoff to palette_finalize if the agent chooses its own final palette. It does not explicitly name when not to use alternatives, but the context is clear enough.

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