All 5 tools have descriptions and basic parameter schemas, but quality is inconsistent. Tool names lack action verbs (minimum_wage_lookup is acceptable, but unfair_dismissal_guide, maternity_paternity_rights, trade_union_directory, labour_court_guide are noun-heavy). Parameters are mostly optional with minimal constraints, no enums, no ranges, no validation guidance. Descriptions are generic ('DEMO' repeated 5 times) and lack actionable context for LLM selection. Output schemas are not documented. Error handling is absent. This is a demo/reference implementation, not production-grade.

• Rename tools to start with action verbs: 'search_minimum_wage' (or 'get_minimum_wage'), 'get_dismissal_rights', 'get_maternity_paternity_rights', 'search_trade_unions', 'get_labour_court_info'.
• Rewrite descriptions to be specific and actionable. Example: 'minimum_wage_lookup' → 'Get Kenya minimum wage rates by sector and county. Returns 2025 statutory rates from Ministry of Labour. Use this to advise workers on wage entitlements.' (avoids 'DEMO', explains when to call it, states what it returns).
• Add enums for all string parameters. E.g., sector: ['general_laborer', 'clerical_officer', 'security_guard', 'domestic_worker', 'teacher', 'agriculture', 'hospitality']; situation: ['no_notice', 'no_reason', 'redundancy', 'summary', 'constructive', 'discrimination'].
• Document output schemas in tool descriptions or as separate schema definitions. Example: 'Returns {source: string, sector: string, county: string, wages: {[key]: {monthly_kes: number, daily_kes: number, note: string}}, note: string}'.
• Add input validation and error messages. If sector is not recognized, return {error: 'Sector not found. Valid sectors: general_laborer, clerical_officer, ...', suggestion: 'Did you mean: general_laborer?'} instead of silently returning a default.