Palette Light and Dark Mode Maps

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

Annotations provide readOnlyHint=true. The description adds behavioral context beyond annotations, detailing the analysis steps (LRV, role assignment, contrast, missing neutrals). This is sufficient for a read-only tool, though edge cases like palette size are not addressed.

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 two sentences, front-loads the main action, and contains no extraneous words. Every sentence adds value.

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 tool has an output schema and only two simple parameters, the description covers the main outputs (role maps) and checks (contrast, missing neutrals). It is largely complete, though return format details are left to the output schema.

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 baseline is 3. The description explains the tool's purpose but does not add parameter-specific details beyond what the schema already provides. The 'use_case' parameter is contextualized but not elaborated.

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 clearly states the tool generates light-mode and dark-mode role maps from a palette, specifying analyses like LRV, role assignment, contrast check, and missing neutrals. It distinguishes itself from sibling palette tools like palette_audit or palette_compare.

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 implies use for generating role maps but does not explicitly state when to use this tool versus alternatives, nor provides exclusion criteria. Sibling tools are numerous, so some guidance would help.

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