C# extension should expose LSP tools to GitHub Copilot

When working with .NET projects in Visual Studio Code, the C# extension should expose LSP-based tools to GitHub Copilot so the assistant can access actual code context instead of relying on file searches, which can sometimes return incorrect information to the model.

For example, the SQL Server extension exposes the following tools to GitHub Copilot; I expect the C# extension to do the same.

Tools such as find_usages, find_references, go_to_implementation, go_to_definition, code_coverage, and perform_build / rebuild / clean.

In Visual Studio (the full IDE), VS exposes find_usages to GitHub Copilot. I would expect the same functionality on the Visual Studio Code side.

This would greatly improve the experience and reduce token usage and external calls. In the screenshot below, GitHub Copilot performs a file-based search instead of using the C# extension’s code-aware tools (for example, go_to_definition), which would locate the interface definition faster and more accurately.