feat: refactored and tweaked model descriptions / schema to use fewer tokens at launch (average reduction per field description: 60-80%) without sacrificing tool effectiveness

Disabled secondary tools by default (for new installations), updated README.md with instructions on how to enable these in .env
run-server.sh now displays disabled / enabled tools (when DISABLED_TOOLS is set)

tools/tracer.py

@@ -38,14 +38,9 @@ logger = logging.getLogger(__name__)
 # Tool-specific field descriptions for tracer workflow
 TRACER_WORKFLOW_FIELD_DESCRIPTIONS = {
     "step": (
-        "Describe what you're currently investigating for code tracing by thinking deeply about the code structure, "
-        "execution paths, and dependencies. In step 1, if trace_mode is 'ask', MUST prompt user to choose between "
-        "precision or dependencies mode with clear explanations. Otherwise, clearly state your tracing plan and begin "
-        "forming a systematic approach after thinking carefully about what needs to be analyzed. CRITICAL: For precision "
-        "mode, focus on execution flow, call chains, and usage patterns. For dependencies mode, focus on structural "
-        "relationships and bidirectional dependencies. Map out the code structure, understand the business logic, and "
-        "identify areas requiring deeper tracing. In all later steps, continue exploring with precision: trace dependencies, "
-        "verify call paths, and adapt your understanding as you uncover more evidence."
+        "The plan for the current tracing step. Step 1: State the tracing strategy. Later steps: Report findings and adapt the plan. "
+        "CRITICAL: For 'precision' mode, focus on execution flow and call chains. For 'dependencies' mode, focus on structural relationships. "
+        "If trace_mode is 'ask' in step 1, you MUST prompt the user to choose a mode."
     ),
     "step_number": (
         "The index of the current step in the tracing sequence, beginning at 1. Each step should build upon or "
@@ -60,46 +55,29 @@ TRACER_WORKFLOW_FIELD_DESCRIPTIONS = {
         "tracing analysis is complete and ready for final output formatting."
     ),
     "findings": (
-        "Summarize everything discovered in this step about the code being traced. Include analysis of execution "
-        "paths, dependency relationships, call chains, structural patterns, and any discoveries about how the code "
-        "works. Be specific and avoid vague language—document what you now know about the code and how it affects "
-        "your tracing analysis. IMPORTANT: Document both the direct relationships (immediate calls, dependencies) "
-        "and indirect relationships (transitive dependencies, side effects). In later steps, confirm or update past "
-        "findings with additional evidence."
+        "Summary of discoveries from this step, including execution paths, dependency relationships, call chains, and structural patterns. "
+        "IMPORTANT: Document both direct (immediate calls) and indirect (transitive, side effects) relationships."
     ),
     "files_checked": (
-        "List all files (as absolute paths, do not clip or shrink file names) examined during the tracing "
-        "investigation so far. Include even files ruled out or found to be unrelated, as this tracks your "
-        "exploration path."
+        "List all files examined (absolute paths). Include even ruled-out files to track exploration path."
     ),
     "relevant_files": (
-        "Subset of files_checked (as full absolute paths) that contain code directly relevant to the tracing analysis. "
-        "Only list those that are directly tied to the target method/function/class/module being traced, its "
-        "dependencies, or its usage patterns. This could include implementation files, related modules, or files "
-        "demonstrating key relationships."
+        "Subset of files_checked directly relevant to the tracing target (absolute paths). Include implementation files, "
+        "dependencies, or files demonstrating key relationships."
     ),
     "relevant_context": (
-        "List methods, functions, classes, or modules that are central to the tracing analysis, in the format "
-        "'ClassName.methodName', 'functionName', or 'module.ClassName'. Prioritize those that are part of the "
-        "execution flow, dependency chain, or represent key relationships in the tracing analysis."
+        "List methods/functions central to the tracing analysis, in 'ClassName.methodName' or 'functionName' format. "
+        "Prioritize those in the execution flow or dependency chain."
     ),
     "confidence": (
-        "Indicate your current confidence in the tracing analysis completeness. Use: 'exploring' (starting analysis), "
-        "'low' (early investigation), 'medium' (some patterns identified), 'high' (comprehensive understanding), "
-        "'very_high' (very comprehensive understanding), 'almost_certain' (nearly complete tracing), "
-        "'certain' (100% confidence - tracing analysis is finished and ready for output with no need for external model validation). "
-        "Do NOT use 'certain' unless the tracing analysis is thoroughly finished and you have a comprehensive understanding "
-        "of the code relationships. Using 'certain' means you have complete confidence locally and prevents external model validation."
+        "Your confidence in the tracing analysis. Use: 'exploring', 'low', 'medium', 'high', 'very_high', 'almost_certain', 'certain'. "
+        "CRITICAL: 'certain' implies the analysis is 100% complete locally and PREVENTS external model validation."
     ),
     "trace_mode": "Type of tracing: 'ask' (default - prompts user to choose mode), 'precision' (execution flow) or 'dependencies' (structural relationships)",
     "target_description": (
-        "Detailed description of what to trace and WHY you need this analysis. MUST include context about what "
-        "you're trying to understand, debug, analyze or find."
-    ),
-    "images": (
-        "Optional images of system architecture diagrams, flow charts, or visual references to help "
-        "understand the tracing context"
+        "Description of what to trace and WHY. Include context about what you're trying to understand or analyze."
     ),
+    "images": ("Optional paths to architecture diagrams or flow charts that help understand the tracing context."),
 }