Server has 13 tools with schemas and descriptions present, but quality is inconsistent. Most tool descriptions are adequate (50-150 chars), but parameter descriptions are sparse or missing context. Critical gaps: no output schemas documented, no error handling guidance, no idempotency hints for destructive operations, and several tools combine multiple concerns (e.g., get_automations does list/toggle/trigger). Parameter naming lacks consistency (e.g., 'action' enum vs explicit verb names). No tool annotations (readOnlyHint, destructiveHint). Schemas are present but lack validation constraints (min/max for numbers, patterns for strings). This is a typical community server with functional but not production-grade definitions.

• Split multi-action tools: replace get_automations with list_automations, toggle_automation, trigger_automation. Same for get_scenes → list_scenes + activate_scene; get_addons → list_addons + install_addon + uninstall_addon + start_addon + stop_addon + restart_addon. Each tool does one thing.
• Document output schemas for all tools. E.g., list_devices returns [{device_id: string, name: string, entity_id: string, state: string, attributes: object}]. Include this in tool descriptions or a separate schema reference.
• Add tool annotations: mark control, call_service, manage_automation_config, get_addons (install/uninstall) with destructiveHint=true. Mark list_devices, get_states, get_history with readOnlyHint=true. Mark idempotent operations with idempotentHint=true.
• Add min/max constraints to numeric parameters in schemas: brightness 0 - 255, position 0 - 100, temperature ranges, humidity 0 - 100. Add enum constraints to command parameter with clear descriptions of which commands apply to which entity types.
• Add error handling guidance: 'If entity_id not found, call list_devices() to discover available entities.' For destructive ops: 'This operation cannot be undone. Confirm before executing.' Provide recovery paths (e.g., undo_automation_config for manage_automation_config).