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

Beyond the readOnlyHint annotation, the description discloses what analysis is performed, what role categories are assigned, what safety checks occur, that rendered downloads are included, and adds an important warning about not presenting archive anchors as recommendations. These are meaningful behavioral constraints beyond the schema.

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 longer than average but every sentence earns its place: it states the action, the analysis, the output, a customer-facing instruction, and a workflow rule. It is front-loaded with the core purpose and remains readable.

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 the annotations mark this as read-only, the description covers the necessary usage context: inputs, processing, delivered outputs, show-to-customer behavior, and follow-up tool routing. Nothing critical is missing for an agent to call this correctly.

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 the schema already documents both parameters well. The description adds general context about how the palette is used, but it does not add express parameter-level semantics beyond the 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?

The description names a specific action ('Generate light-mode and dark-mode role maps from a palette') and details the analysis (LRV, role assignment, contrast safety, flagging missing neutrals). This clearly distinguishes it from sibling palette tools by its role-maping scope.

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 first sentence gives clear context for when to use the tool: when a palette needs light/dark role maps. It also provides explicit follow-up guidance about calling palette_finalize if the agent selects its own final palette, though it does not enumerate exclusions or compare against sibling palette tools.

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