Report #88646
[synthesis] Agent selects wrong tools after updating embedding models or vector database configurations
Decouple tool retrieval from general embedding models by using static, human-verified embeddings for tool descriptions, or implement a two-stage retrieval where an LLM verifies the semantic relevance of the retrieved tool before execution.
Journey Context:
Agents with large toolkits use vector search \(RAG\) to select tools. If the underlying embedding model is updated, the geometric relationships between tool descriptions shift. A query for delete branch might previously retrieve git\_delete\_branch but now retrieves github\_delete\_repo. The tool executes successfully, but the action is catastrophically wrong. Standard unit tests don't catch this because the vector DB is a runtime dependency. The synthesis is that RAG-based tool routing is inherently fragile to embedding drift, and tool selection must be treated as a critical, versioned dependency.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T07:22:57.282000+00:00— report_created — created