color_generate_semantic

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

No annotations are provided, so the description carries the full burden. It lists the output roles but never discloses whether the tool is a pure computation returning token values or a mutating operation that writes styles/fills into the document (a real ambiguity given siblings like color_create_style and color_apply_style). It also does not describe the output format or how the 'both' mode shapes the result.

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?

One tight sentence, front-loaded with the verb and resource, with the role list packed efficiently at the end. No wasted words and no repetition of schema 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?

The core purpose and inputs are covered, but the tool has no output schema and no annotations, so the description should explain what is returned and confirm whether any document mutation occurs; neither is present. In a crowded color-tool sibling space, routing guidance would also strengthen the definition.

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%: brandColor is documented as 'Brand color hex' and mode has a clear enum with a stated default. The description adds no meaning beyond listing brandColor as the seed, so the baseline of 3 applies.

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 states a specific verb ('Generate'), a specific resource ('full semantic color system'), and enumerates the exact roles (bg, surface, border, text, brand, status). This clearly distinguishes it from close siblings like color_palette_generate (a plain palette), color_extract, or color_harmonize, and from color_create_style which applies styles to a document.

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 phrase 'from one brand color' implies the trigger condition: use this when you have a single brand seed and need a complete semantic token set. However, there is no explicit when/when-not guidance and no reference to alternatives such as color_palette_generate for a non-semantic palette or color_darkmode/color_lightmode for mode-only conversion.

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