Problem: The \mslearn search --json\ output includes title, url, and content, but the source product or technology area (e.g., Azure, .NET, VS Code) is not explicitly surfaced. LLMs must infer it from the URL or content, which is unreliable.
Solution: Include a \product\ or \source\ field in the search result JSON output, derived from the document metadata already available in the Learn API.
Use case: An agent using \mslearn search --json | jq\ to filter results by product before deciding which to fetch would benefit from an explicit \product\ field rather than parsing URLs.
Problem: The \mslearn search --json\ output includes title, url, and content, but the source product or technology area (e.g., Azure, .NET, VS Code) is not explicitly surfaced. LLMs must infer it from the URL or content, which is unreliable.
Solution: Include a \product\ or \source\ field in the search result JSON output, derived from the document metadata already available in the Learn API.
Use case: An agent using \mslearn search --json | jq\ to filter results by product before deciding which to fetch would benefit from an explicit \product\ field rather than parsing URLs.