simulateColorConvert a hex color to how it appears for protan, deutan, or tritan color blindness.
Return how a single hex color appears to someone with a given type of color blindness (protan, deutan, or tritan).
| Name | Required | Description | Default |
|---|---|---|---|
| type | Yes | Color-vision deficiency type | |
| color | Yes | Hex color, e.g. #d7191c |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses the input domain (single hex color, one of three deficiency types) and the general nature of the result, but says nothing about the output representation, whether results are approximate, or that the operation is side-effect free.
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?
A single front-loaded sentence with zero filler; the verb, scope, and accepted inputs all land immediately.
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?
With no output schema, the description should clarify the return shape (e.g. resulting hex or RGB triplet), which it does not. It is otherwise adequate for a simple two-parameter pure function.
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 coverage is 100% and both parameters are already documented with enum and example format in the schema. The description restates the three enum values and the hex format without adding syntax, defaults, or edge-case behavior 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?
States a specific verb and resource: returning how one hex color appears under a named color-vision deficiency. It is clearly distinguishable from palette/contrast siblings by scope (single color simulation). Sibling differentiation is implicit rather than explicit, so not a 5.
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?
No guidance on when to pick this over checkContrast, checkPalette, or generateSafePalette, and no prerequisites stated. Usage is only inferable from the phrase 'single hex color'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.