13 tools with consistent verb_noun naming (hue_get_*, hue_list_*, hue_set_*). All tools have descriptions (avg ~60 chars, baseline 194). Input schemas present with type definitions for all parameters. However, descriptions are significantly below baseline (60 vs 194 chars), too terse to guide LLM selection. Parameter descriptions are minimal (10-30 chars vs baseline 72). No output schemas documented. No error handling guidance. Missing tool annotations (readOnlyHint/destructiveHint). Risk labels present but not integrated into schema.

• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. E.g., 'Get the current state of a single light (on/off, brightness, color). Use this to check a light's status before controlling it. Returns light object with id, name, state, and color info.'
• Add format constraints to parameter descriptions. E.g., 'Light name or UUID (e.g., 'Living Room Lamp' or '550e8400-e29b-41d4-a716-446655440000'). If unsure, call hue_list_lights first.'
• Document output schemas for all tools. E.g., hue_list_lights returns {lights: [{id, name, state: {on, brightness, color}, room_id}], total_count}. Include pagination if applicable.
• Add tool annotations to schema. Mark hue_set_* tools with destructiveHint=true. Mark hue_get_* and hue_list_* with readOnlyHint=true. Mark idempotent operations with idempotentHint=true.
• Add error handling guidance. E.g., 'If light not found, returns error 'Light not found: <name>. Call hue_list_lights to see available lights.' If color format invalid, returns 'Invalid color format: <value>. Use hex (#FF8000), Kelvin (3000K), or name (warm, cool).'

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

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