This is Part 10 of my series on the Microsoft Agent Framework. You can read the original post over on lukaswalter.dev . So far, our agent can answer questions, stream responses, remember history, reduce context, use tools, return structured output, connect to MCP and load Agent Skills. That is already a lot. And that is exactly where the next problem starts. It is tempting to keep adding instructions and tools to one large agent. Make it a coding assistant. Also make it a music expert. Also make it answer questions about coffee. Also give it support tools, documentation tools and internal process rules. At some point, the agent becomes a jack of all trades. The prompt grows. The tool list grows. The model has more irrelevant instructions to ignore. And you pay for unnecessary input tokens on every request, even when the user only asks a simple question. One practical way out is manual routing.…