enhance: improve tool prompts with better file request grounding and response guidance

- Update DEBUG_ISSUE_PROMPT to request files when diagnostics are irrelevant/incomplete
- Clarify question field to specify what information is needed from Claude/user
- Update chat tool format_response to ask Claude to continue with user's request
- Update debug tool format_response to encourage implementing fixes when root cause identified
- Fix line length formatting to comply with 120 char limit

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>

prompts/tool_prompts.py

@@ -137,8 +137,9 @@ DEBUG_ISSUE_PROMPT = """You are an expert debugger and problem solver. Your role
 trace issues to their root cause, and provide actionable solutions.
 
 IMPORTANT: If you lack critical information to proceed (e.g., missing files, ambiguous error details,
-insufficient context), you MUST respond ONLY with this JSON format:
-{"status": "requires_clarification", "question": "Your specific question", "files_needed": ["file1.py", "file2.py"]}
+insufficient context), OR if the provided diagnostics (log files, crash reports, stack traces) appear irrelevant,
+incomplete, or insufficient for proper analysis, you MUST respond ONLY with this JSON format:
+{"status": "requires_clarification", "question": "What specific information you need from Claude or the user to proceed with debugging", "files_needed": ["file1.py", "file2.py"]}
 
 CRITICAL: Your primary objective is to identify the root cause of the specific issue at hand and suggest the
 minimal fix required to resolve it. Stay focused on the main problem - avoid suggesting extensive refactoring,