conductor-figma has 6 tools with basic schemas and descriptions, but significant quality gaps. Tool names lack consistent verb prefixes (e.g., 'suggest_color_palette' vs 'get_design_craft_guide'). Descriptions are present but generic (avg ~80 chars, below 194-char baseline). Input schemas exist but lack depth: most parameters have minimal descriptions, no enums for constrained inputs (e.g., 'mode' in suggest_color_palette accepts 'dark'|'light' but this is not formalized), and no output schemas documented. Error handling is minimal, handlers catch exceptions but provide no recovery guidance. The 'design_from_prompt' tool is destructive (WRITE risk) but has no confirmation pattern or dry-run option. No tool annotations (readOnlyHint/destructiveHint) despite clear read/write distinction.

• Add enum constraints to 'mode' parameter in suggest_color_palette and suggest_type_scale. Change schema from {type:'string'} to {type:'string', enum:['dark','light']}.
• Document output schemas for all tools. E.g., check_contrast should return {type:'object', properties:{ratio:{type:'number'}, level:{type:'string', enum:['AAA','AA','fail']}}}.
• Expand parameter descriptions to 50-100 chars with format/range hints. E.g., 'brandColor: Brand color in hex format (e.g., #FF5733, 6 hex digits)'.
• Add confirmation pattern to design_from_prompt: accept optional 'dry_run' parameter that returns preview without persisting, or require explicit 'confirm:true' flag.
• Annotate tools with readOnlyHint/destructiveHint in tool definitions. Mark design_from_prompt with destructiveHint:true and others with readOnlyHint:true.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry