Two tools with critical definition gaps. elgato_key_light_control_tool has a vague description and parameters with NO descriptions (on, brightness, temperature all have null descriptions). elgato_key_light_status_tool has a reasonable description but empty input schema. Neither tool documents output structure. Parameter types are present but lack semantic guidance (e.g., 'on' as integer is ambiguous, should be boolean or enum 0/1). No error handling guidance. No parameter constraints (brightness 0-100, temperature 143-344 mentioned in description but not in schema). Descriptions are 10 - 20 chars below the 194-char baseline for production tools.

• Add descriptions to all parameters in elgato_key_light_control_tool: 'on' → 'Set light state: 1 for on, 0 for off', 'brightness' → 'Brightness level (0 - 100, where 0 is off and 100 is maximum)', 'temperature' → 'Color temperature in Kelvin scale (143=7000K, 344=2900K)'.
• Change 'on' parameter type from integer to enum with values [0, 1] and descriptions, or switch to boolean type with clear mapping.
• Document output schemas: elgato_key_light_control_tool should return {success: boolean, response_code: integer, message: string}; elgato_key_light_status_tool should return {lights: [{on: integer, brightness: integer, temperature: integer}]}.
• Add min/max constraints to schema: brightness {type: integer, minimum: 0, maximum: 100}, temperature {type: integer, minimum: 143, maximum: 344}.
• Enhance error responses with recovery hints: 'Failed to connect to light at 192.168.100.13:9123. Check ELGATO_LIGHT_HOST environment variable and network connectivity.' Include retryable vs fatal classification.