Fix agentic-tools.md: remove duplicate walkthrough, clarify VS Code scope, explain why plugin is needed

- Remove duplicate 'Walkthrough' section (full setup guide pasted in,
  creating a broken level-1 heading mid-document and duplicating content
  already in get-started/ai-setup.md)
- Add NOTE: VS Code cannot build/debug WinUI 3 apps; Visual Studio
  required for MSIX build tooling and WinUI project templates
- Add 'Why does Copilot need these tools?' section explaining the
  UWP/WinUI 3 training data gap honestly — not a framework quality
  problem, a training data distribution problem that the plugin fixes
- Replace embedded how-to content with a clean link to ai-setup.md
- Add Related content section linking to the get-started cluster
- ms.topic: article -> how-to (accurate taxonomy)

Co-authored-by: Copilot <[email protected]>

Author: GrantMeStrength

hub/apps/dev-tools/agentic-tools.md

@@ -1,8 +1,8 @@
 ---
 title: Agentic AI tools for Windows development
 description: Learn how to enhance AI coding agents with Windows-specific context using MCP servers, custom instructions, and community plugins.
-ms.date: 03/03/2026
-ms.topic: article
+ms.date: 03/11/2026
+ms.topic: how-to
 ---
 
 # Agentic AI tools for Windows development
@@ -51,8 +51,27 @@ The plugin includes:
 copilot plugin install winui3-development@awesome-copilot
 ```
 
-This copies the plugin's agents, skills, and instructions into your project's `.github/` directory, where Copilot picks them up automatically.
+This copies the plugin's agents, skills, and custom instructions into your project's `.github/` directory, where Copilot picks them up automatically.
+
+> [!NOTE]
+> WinUI 3 apps require **Visual Studio** for building and debugging — VS Code does not have the required MSIX build tooling or WinUI project templates. However, if you're using VS Code to work on other Windows frameworks (Electron, Flutter, .NET, or Rust with winapp CLI), this plugin still provides useful Windows App SDK context for those scenarios.
 
 **Browse and discover more plugins:**
 
-You can browse all available Copilot customizations using the [Awesome Copilot extension for VS Code](https://marketplace.visualstudio.com/items?itemName=TimHeuer.awesome-copilot), which lets you preview and install resources directly into your workspace.
+You can browse all available Copilot customizations using the [Awesome Copilot extension for VS Code](https://marketplace.visualstudio.com/items?itemName=TimHeuer.awesome-copilot), which lets you preview and install resources directly into your workspace.
+
+## Why does Copilot need these tools?
+
+Copilot's code suggestions are shaped by its training data. Because UWP has many more years of community samples, tutorials, and Stack Overflow answers than WinUI 3, Copilot may default to UWP patterns — such as `Windows.UI.Xaml` namespaces, `CoreDispatcher`, or `MessageDialog` — when you ask about Windows UI development. This isn't a quality problem with WinUI 3; it reflects a training data distribution gap that's common with any newer framework.
+
+The WinUI 3 plugin addresses this directly: its custom instructions give Copilot explicit, up-to-date rules about current Windows App SDK patterns, so it generates correct code without you needing to prompt around its knowledge gaps. Combined with the Learn MCP Server's live documentation access, Copilot has the context it needs to be genuinely useful for Windows development.
+
+## Set up step-by-step
+
+For a complete walkthrough — including IDE setup, agent mode, MCP server configuration, and verification — see [Set up GitHub Copilot for Windows development](../get-started/ai-setup.md).
+
+## Related content
+
+- [Set up GitHub Copilot for Windows development](../get-started/ai-setup.md)
+- [AI-assisted Windows development](../get-started/ai-for-windows-devs.md)
+- [GitHub Copilot in Visual Studio](../how-tos/github-copilot-winui-vs.md)