refactor(@angular/cli): remove modernize tool and add instructions for schematic discovery

Remove the `modernize` tool from the Angular CLI MCP server, as it is largely redundant with the
official Angular developer skill and direct usage of schematics. To compensate for this removal,
add instructions to the server describing how agents can use `ng generate <package>: --help` to
discover available modernization schematics. This simplifies the codebase while maintaining the
ability for agents to perform code modernization.

Author: clydin

packages/angular/cli/src/commands/mcp/mcp-server.ts

@@ -21,7 +21,7 @@ import { DEVSERVER_STOP_TOOL } from './tools/devserver/devserver-stop';
 import { DEVSERVER_WAIT_FOR_BUILD_TOOL } from './tools/devserver/devserver-wait-for-build';
 import { DOC_SEARCH_TOOL } from './tools/doc-search';
 import { E2E_TOOL } from './tools/e2e';
-import { MODERNIZE_TOOL } from './tools/modernize';
+
 import { ZONELESS_MIGRATION_TOOL } from './tools/onpush-zoneless-migration/zoneless-migration';
 import { LIST_PROJECTS_TOOL } from './tools/projects';
 import { TEST_TOOL } from './tools/test';
@@ -51,7 +51,7 @@ const STABLE_TOOLS = [
 export const EXPERIMENTAL_TOOLS = [
   BUILD_TOOL,
   E2E_TOOL,
-  MODERNIZE_TOOL,
+
   TEST_TOOL,
   ...DEVSERVER_TOOLS,
 ] as const;
@@ -105,6 +105,12 @@ equivalent actions.
 
 * **3. Answer User Questions:**
     - For conceptual questions ("what is..."), use \`search_documentation\`.
+
+* **4. Discover Schematics for Modernization:** Since this server does not provide a
+  specific tool for listing available schematics, you can use a shell command (if
+  available) with \`ng generate <package-name>: --help\` to discover what migrations
+  are available in a package (e.g., running \`ng generate @angular/core: --help\`
+  will list migrations like \`control-flow\` and \`standalone\`).
 </Core Workflows & Tool Guide>
 
 <Key Concepts>

packages/angular/cli/src/commands/mcp/tools/modernize.ts

@@ -44,8 +44,8 @@ most important action to take in the migration journey.
 * **Iterative Process:** The migration process is iterative. You must call this tool repeatedly,
   applying the suggested fix after each call, until the tool indicates that no more actions are
   needed.
-* **Relationship to \`modernize\`:** This tool is the specialized starting point for the zoneless/OnPush
-  migration. For other migrations (like signal inputs), you should use the \`modernize\` tool first,
+* **Relationship to other migrations:** This tool is the specialized starting point for the zoneless/OnPush
+  migration. For other migrations (like signal inputs), you should run the corresponding schematics first,
   as the zoneless migration may depend on them as prerequisites.
 * **Input:** The tool can operate on either a single file or an entire directory. Provide the
   absolute path.