Skill: agent skips Learn MCP tools because discovery is not explicit

Problem

When executing the "What's new for my project?" workflow, the agent skips step 4 (Query Learn MCP Server) entirely. It has the Learn MCP tools available (microsoft_docs_search, microsoft_docs_fetch, microsoft_code_sample_search) via the plugin's bundled .mcp.json, but never checks its own tool list and defaults to session catalog only.

When prompted, the agent jumped to the CLI fallback (npx @microsoft/learn-cli) without first checking whether the MCP tools were available. The root cause: the skill says what to use but not how the agent discovers it at runtime.

Observed behavior

1. Agent reads skill, identifies workflow steps
2. Agent executes session catalog search (step 3)
3. Agent skips Learn docs entirely (step 4)
4. When asked why, agent reports: "The MCP tools don't appear in my top-level tool list. They exist but require active discovery. The skill assumes the agent will find them automatically."

Suggested fixes

1. Add explicit discovery instruction early in the skill: "Before executing workflows, verify Learn MCP tools are available by searching your tool list for microsoft_docs. If found, use them. If not, fall back to the CLI."

2. Reorder or parallelize steps 3-4: The current ordering (catalog first, Learn second) signals priority. If the skill said "steps 3-4 run in parallel" or listed Learn first (it is always available; the catalog is event-dependent), agents would be less likely to skip it.

Impact

Every user whose query would benefit from Learn docs (SDK updates, what's-new pages, migration guides) gets incomplete answers. The session catalog and news index compensate partially, but product-specific documentation is invisible unless the user explicitly asks for it.

Repro

> what is new at Build 2026 for my project?
# Agent fetches news + sessions, never queries Learn
> Why did you not search Learn docs?
# Agent admits it skipped step 4 and did not discover the MCP tools

Locate the skill definition and inspect the bundled .mcp.json entry for the Learn tools; compare the workflow's session-catalog and Learn steps. Done means the skill explicitly explains runtime discovery, use of the Learn tools when available, the npx @microsoft/learn-cli fallback, and the intended ordering or parallel execution.