AssetGenie has 5 tools with complete schemas and descriptions, but significant quality gaps limit production readiness. Tool names lack clear action verbs (audit_health, sync_localization, generate_constants are acceptable but generic). Descriptions are present (avg ~150 chars) but lack actionable context for LLM selection. Parameter descriptions exist but are sparse, many lack format constraints, ranges, or dependency documentation. No output schemas documented. Error handling is minimal; handlers return generic TextContent without structured recovery guidance. The app_harness tool's handler code is incomplete in the provided source, making full assessment impossible.

• Document output schemas for all 5 tools. E.g., audit_health should return {issues: [{type: string, file: string, severity: string}], summary: {total_issues: number, large_files: number}}.
• Add min/max constraints to numeric parameters. E.g., max_size_kb: {type: 'number', minimum: 1, maximum: 100000, description: '...'}.
• Enhance error responses with recovery guidance. Instead of 'Error: invalid path', return 'Error: project_path does not exist. Verify the path is absolute and the Flutter project root contains pubspec.yaml.'
• Rename tools for clarity: 'audit_health' → 'scan_asset_health', 'sync_localization' → 'merge_translations', 'audit_localization' → 'validate_translations'.
• Add parameter descriptions for enum values. E.g., action enum should document: 'get_widget_tree: inspect widget hierarchy; capture_screenshot: save UI snapshot; get_logs: retrieve console output'.