feat(angular-toolkit-mcp): improve schemas

Author: Karnaukhov-kh

packages/angular-mcp-server/src/lib/tools/ds/report-violations/report-all-violations.tool.ts

@@ -33,12 +33,12 @@ interface ReportAllViolationsOptions extends BaseHandlerOptions {
 export const reportAllViolationsSchema = {
   name: 'report-all-violations',
   description:
-    'Scan a directory for deprecated design system CSS classes defined in the config at `deprecatedCssClassesPath`, and output a usage report',
+    'Scan a directory for all deprecated design system CSS classes and output a comprehensive violation report. Use this to discover all violations across multiple components. Output can be grouped by component (default) or by file, and includes: file paths, line numbers, violation details, and replacement suggestions (which component should be used instead). This is ideal for getting an overview of all violations in a directory.',
   inputSchema: createProjectAnalysisSchema({
     groupBy: {
       type: 'string',
       enum: ['component', 'file'],
-      description: 'How to group the results: "component" groups by design system component, "file" groups by file path',
+      description: 'How to group the results: "component" (default) groups by design system component showing all files affected by each component, "file" groups by file path showing all components violated in each file',
       default: 'component',
     },
   }),

packages/angular-mcp-server/src/lib/tools/ds/report-violations/report-violations.tool.ts

@@ -19,7 +19,7 @@ interface ReportViolationsOptions extends BaseHandlerOptions {
 
 export const reportViolationsSchema = {
   name: 'report-violations',
-  description: `Report deprecated DS CSS usage in a directory with configurable grouping format.`,
+  description: `Report deprecated CSS usage for a specific design system component in a directory. Returns violations grouped by file, showing which deprecated classes are used and where. Use this when you know which component you're checking for. Output includes: file paths, line numbers, and violation details (but not replacement suggestions since the component is already known).`,
   inputSchema: createViolationReportingSchema(),
   annotations: {
     title: 'Report Violations',

packages/angular-mcp-server/src/lib/tools/ds/shared/models/schema-helpers.ts

@@ -8,18 +8,18 @@ export const COMMON_SCHEMA_PROPERTIES = {
   directory: {
     type: 'string' as const,
     description:
-      'The relative path to the directory (starting with "./path/to/dir") to scan. Respect the OS specifics.',
+      'The relative path to the directory (starting with "./path/to/dir") to scan. Respect the OS specifics. Should point to the directory containing the files you want to analyze for violations.',
   },
 
   componentName: {
     type: 'string' as const,
-    description: 'The class name of the component (e.g., DsButton)',
+    description: 'The class name of the design system component to check for violations (e.g., DsButton, DsBadge, DsCard). This should be the TypeScript class name, not the selector.',
   },
 
   groupBy: {
     type: 'string' as const,
     enum: ['file', 'folder'] as const,
-    description: 'How to group the results',
+    description: 'How to group the violation results in the output. "file" groups violations by individual file paths, "folder" groups by directory structure.',
     default: 'file' as const,
   },
 } as const;