Single tool with minimal definition quality. Tool name 'extract_clean_json' lacks action verb clarity (should be 'extract_json' or 'parse_json'). Description is adequate (73 chars) but lacks WHEN/WHY guidance. Input schema present but parameter 'raw_text' has no description, violates pattern:tool-description. No output schema documented. No error handling guidance. Tool does one thing well but definition falls short of production standards.

• Add description to 'raw_text' parameter: 'Raw text that may contain markdown code fences (```json ... ```), narrative text, or bare JSON. Tool extracts and parses the JSON payload.'
• Document output schema: 'Returns a JSON object with the extracted and parsed payload. Structure depends on input; no fixed schema enforced.'
• Enhance tool description to 50-150 chars: 'Extracts valid JSON from LLM outputs containing markdown fences, narrative text, or mixed content. Use when LLM wraps JSON in ```json ... ``` blocks.'
• Improve error message: 'Could not extract valid JSON. Input may lack markdown fences (```json ... ```) or valid JSON object. Ensure input contains either: (1) bare JSON, (2) ```json ... ``` fence, or (3) text with outermost {...} braces.'
• Consider renaming to 'parse_json' or 'extract_json' for clarity and verb-first convention.