diff --git a/docs/ds-refactoring-flow.md b/docs/ds-refactoring-flow.md
index fcaeedd..bbd19c5 100644
--- a/docs/ds-refactoring-flow.md
+++ b/docs/ds-refactoring-flow.md
@@ -65,7 +65,7 @@ This rule follows a two-step process to find violations:
 ### Tools used
 
 - `report-violations` - Main MCP tool that analyzes deprecated design system CSS usage
-  - Parameters: `componentName`, `directory`, `groupBy` (folder/file)
+  - Parameters: `componentName`, `directory`, `groupBy` (folder/file), `excludePatterns` (optional glob pattern(s) to exclude files/directories)
   - Returns violation data with counts and locations
   - Supports both folder-level and file-level grouping
 
@@ -122,7 +122,7 @@ This rule follows a comprehensive two-step process to find all violations:
 ### Tools used
 
 - `report-all-violations` - Comprehensive MCP tool that analyzes all deprecated design system CSS usage across the codebase
-  - Parameters: `directory`, `groupBy` (folder/file)
+  - Parameters: `directory`, `groupBy` (folder/file), `excludePatterns` (optional glob pattern(s) to exclude files/directories)
   - Returns: Complete violation data with counts and locations across all components
   - Supports both folder-level overview and file-level detailed analysis
 
@@ -386,7 +386,7 @@ The rule implements a systematic three-phase process for handling non-migratable
   - Used for: Discovery phase and validation of CSS count consistency
 
 - `report-violations` - Analyzes deprecated component usage in templates and code
-  - Parameters: `directory`, `componentName`  
+  - Parameters: `directory`, `componentName`, `excludePatterns` (optional)
   - Returns: List of component violations with file locations
   - Used for: Validation of violation reduction after implementation
 
@@ -715,7 +715,7 @@ This rule follows a three-step analysis process:
   - Scans: .scss, .sass, .less, .css files for deprecated class selectors
 
 - `report-violations` - Analyzes deprecated component usage in templates and code
-  - Parameters: `directory`, `componentName`
+  - Parameters: `directory`, `componentName`, `excludePatterns` (optional)
   - Returns: List of component violations with file locations and line numbers
   - Scans: .html, .ts files for deprecated component usage in templates and inline templates
 
diff --git a/docs/tools.md b/docs/tools.md
index e6cbf16..761cd4d 100644
--- a/docs/tools.md
+++ b/docs/tools.md
@@ -13,6 +13,7 @@ This document provides comprehensive guidance for AI agents working with Angular
 - `directory`: Target analysis directory (use relative paths like `./src/app`)
 - `componentName`: Component class name (e.g., `DsButton`)
 - `groupBy`: `"file"` or `"folder"` for result organization
+- `excludePatterns`: Optional glob pattern(s) to exclude files/directories from scanning. Supports standard glob syntax (`*`, `**`, `?`). Can be a single string or array of strings (e.g., `"node_modules/**"`, `["**/dist/**", "**/*.spec.ts"]`)
 - `saveAsFile`: Optional boolean - if `true`, saves report to `tmp/.angular-toolkit-mcp/violations-report/<componentName>/<directory>-violations.json`
 **Output**: 
 - Default: Structured violation reports grouped by file or folder
@@ -25,6 +26,7 @@ This document provides comprehensive guidance for AI agents working with Angular
 **Key Parameters**:
 - `directory`: Target analysis directory (use relative paths like `./src/app`)
 - `groupBy`: `"component"` or `"file"` for result organization (default: `"component"`)
+- `excludePatterns`: Optional glob pattern(s) to exclude files/directories from scanning. Supports standard glob syntax (`*`, `**`, `?`). Can be a single string or array of strings (e.g., `"node_modules/**"`, `["**/dist/**", "**/*.spec.ts"]`)
 - `saveAsFile`: Optional boolean - if `true`, saves report to `tmp/.angular-toolkit-mcp/violations-report/<directory>-violations.json`
 **Output**: 
 - Default: Structured violation reports grouped by component or file covering all components