Skip to content

[TypeSpec Authoring] Resolve conflict between agentic-search Fallback and Case 3 in authoring-plan.md #16317

Description

@haolingdong-msft

Problem

In authoring-plan.md, the newly added agentic-search Fallback conflicts with the Case 3 instruction, which can dead-end the workflow when external URLs are unreachable.

  • The Fallback says:

    Fallback: If agentic search fails (all URLs unreachable or timeout exceeded), proceed with the MCP tool result alone. Do not block the workflow on unreachable external documentation.

  • But Case 3 — API Version Evolution says:

    Must use Agentic Search (option 2 above) to build the plan — do not call the MCP tool.

For Case 3, when all URLs are unreachable, the Fallback tells the agent to proceed with the MCP tool result, while Case 3 forbids calling the MCP tool — leaving no valid path forward.

Expected

Resolve the contradiction so Case 3 has a well-defined behavior when agentic search fails. For example, explicitly allow the Case 3 flow to fall back to the MCP tool result (or another defined degraded path) instead of dead-ending.

Reference

Copilot review comment: #15840 (comment)

Metadata

Metadata

Labels

AzSDK Tools AgentIssue related to the AzSDK Tools Agent.

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions