78 tools with severe definition gaps. Examined tools/automations.py, tools/lights.py, tools/system.py, tools/alarm.py, and others. Most tools lack visible input schemas in source code, parameter types and descriptions are not declared in the tool registration. Descriptions exist but are minimal (10-50 chars typically), providing little context for LLM selection. No evidence of enum constraints, format specifications, or parameter validation guidance. Error handling is absent, no recovery hints or actionable error messages. Tool names follow verb_noun convention (good), but lack of schema visibility and sparse descriptions prevent confident LLM reasoning. High-risk tools (restart_home_assistant, delete_automation, unlock_door) have no confirmation patterns or permission gates visible.

• Add explicit JSON Schema input definitions to all 78 tools with type, description, enum, and format constraints. Use @mcp.tool() decorator with full InputModel or inline schema.
• Expand tool descriptions to 50-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and what it returns. Example: 'Turn on a light by entity_id or name. Returns brightness, color, and state. Use before turn_off_light to toggle.'
• Add enum constraints for all categorical parameters (e.g., alarm_mode: [arm_away, arm_home, disarm], light_brightness: 0-255). Document in parameter descriptions.
• Implement confirmation pattern for destructive tools: add a 'confirm' boolean parameter or return a confirmation token requiring a second call. Prevents accidental deletions and system restarts.
• Add pagination to all list_* tools: accept limit (1-100, default 20) and offset/cursor parameters. Return total_count and next_cursor in response. Document in tool description.