📚 Get comprehensive guidance on effectively using code analysis tools.

🎯 PURPOSE: Provides detailed instructions, best practices, and workflow recommendations for optimal tool usage. 🔧 USAGE: Call this FIRST if you need guidance on tool selection, sequencing, or best practices. ⚡ PERFORMANCE: Lightweight operation - provides strategic guidance without analysis overhead. 🔄 WORKFLOW: Use before starting complex analysis tasks to understand optimal tool orchestration.

🔍 Perform comprehensive codebase analysis with metrics and structure overview.

🎯 PURPOSE: Builds the foundational code graph and provides project-wide insights including file counts, language distribution, complexity metrics, and architectural overview. 🔧 USAGE: Run this FIRST before using other analysis tools - it builds the code graph that powers all subsequent operations. ⚡ PERFORMANCE: Expensive operation (10-60s for large codebases) - results are cached for subsequent tool calls. Progress is shown during analysis. 🔄 WORKFLOW: analyze_codebase → specific analysis tools (find_definition, complexity_analysis, etc.) → insights and recommendations. 💡 TIP: Use rebuild_graph=true only if code has changed significantly since last analysis.

🎯 Find the definition location of a symbol (function, class, variable, method).

🎯 PURPOSE: Locates where a symbol is originally defined, providing file path, line number, and context. 🔧 USAGE: Use after analyze_codebase when you need to understand where a specific symbol is implemented. ⚡ PERFORMANCE: Fast operation (sub-second) - leverages cached code graph for instant lookups. 🔄 WORKFLOW: analyze_codebase → find_definition → examine definition context → find_references/find_callers for usage patterns. 💡 TIP: Works with partial names - 'MyClass' will find 'MyClass', 'MyClassImpl', etc. Use exact names for precision.

📍 Find all references to a symbol throughout the codebase.

🎯 PURPOSE: Discovers everywhere a symbol is used, imported, or referenced, showing usage patterns and dependencies. 🔧 USAGE: Use after find_definition to understand how a symbol is used across the codebase. ⚡ PERFORMANCE: Fast operation (1-3s) - efficiently searches the indexed code graph. 🔄 WORKFLOW: find_definition → find_references → analyze usage patterns → complexity_analysis for refactoring insights. 💡 TIP: Essential for impact analysis before refactoring - shows all code that would be affected by changes.

📞 Find all functions that call the specified function.

🎯 PURPOSE: Identifies the call hierarchy - which functions depend on the target function, essential for understanding code dependencies. 🔧 USAGE: Use when analyzing function dependencies, planning refactoring, or understanding code flow patterns. ⚡ PERFORMANCE: Fast operation (1-2s) - uses pre-built call graph for efficient traversal. 🔄 WORKFLOW: find_definition → find_callers → analyze call patterns → find_callees for complete dependency picture. 💡 TIP: Crucial for refactoring - shows all functions that would break if you change the target function's signature.

📱 Find all functions called by the specified function.

🎯 PURPOSE: Maps function dependencies - what other functions does the target function rely on, revealing complexity and coupling. 🔧 USAGE: Use to understand function complexity, identify potential extraction opportunities, or analyze dependency chains. ⚡ PERFORMANCE: Fast operation (1-2s) - leverages indexed call relationships for instant results. 🔄 WORKFLOW: find_definition → find_callees → complexity_analysis → identify refactoring opportunities. 💡 TIP: High callee count often indicates functions that are doing too much and could benefit from decomposition.

📊 Analyze code complexity and identify refactoring opportunities.

🎯 PURPOSE: Calculates cyclomatic complexity, identifies code smells, and suggests specific refactoring opportunities with priority rankings. 🔧 USAGE: Use after basic analysis to identify problematic code areas that need attention. Essential for code quality assessment. ⚡ PERFORMANCE: Moderate operation (5-15s) - analyzes complexity metrics across the entire codebase. 🔄 WORKFLOW: analyze_codebase → complexity_analysis → examine high-complexity functions → find_callers/find_callees for refactoring impact. 💡 TIP: Start with threshold=15 for critical issues, lower to 10 for comprehensive analysis. Focus on functions with complexity >20 first.

🔗 Analyze module dependencies and import relationships.

🎯 PURPOSE: Maps module interdependencies, identifies circular dependencies, and reveals architectural patterns and potential issues. 🔧 USAGE: Use for architectural analysis, identifying tightly coupled modules, or planning module restructuring. ⚡ PERFORMANCE: Moderate operation (3-10s) - analyzes import relationships and builds dependency graph. 🔄 WORKFLOW: analyze_codebase → dependency_analysis → identify problematic dependencies → complexity_analysis for detailed insights. 💡 TIP: Look for circular dependencies and modules with high fan-in/fan-out ratios - these often indicate architectural problems.

📈 Get comprehensive project statistics and health metrics.

🎯 PURPOSE: Provides high-level project overview including file counts, language distribution, complexity trends, and overall health score. 🔧 USAGE: Use for project assessment, progress tracking, or generating project reports. Great for understanding project scale and characteristics. ⚡ PERFORMANCE: Fast operation (1-3s) - aggregates pre-calculated metrics from the code graph. 🔄 WORKFLOW: analyze_codebase → project_statistics → drill down with specific analysis tools based on findings. 💡 TIP: Use regularly to track code quality trends over time. Health score below 7/10 indicates areas needing attention.