Back to CatalogHero Agent is the mistake of continuously piling new tools and instructions into a single monolithic agent instead of extracting focused specialists.
Agentic AI
Anti-Patterns
Hero Agent
Stuffing every capability into one agent with one giant prompt — and watching quality collapse as it grows.
Intent & Description
🎯 Intent
One agent absorbs every capability (email, calendar, research, file editing) via an ever-growing system prompt and tool list, because splitting “feels like premature optimization.”
📋 Context
It starts small and wins use cases. Each new feature gets appended. A year later the system prompt is 1,000+ lines, there are 40 registered tools, and every new capability regresses the ones before it.
💡 Solution
Once the prompt exceeds a few hundred lines or tool count exceeds ~12, extract specialists. See routing, supervisor, multi-model-routing.
Real-world Use Case
- Never use this; once the prompt grows past a few hundred lines or tool count exceeds about a dozen, extract specialists.
- Use routing, supervisor, or multi-model-routing to split capability across focused agents.
- Treat single-prompt sprawl as a code smell, not a destination.
Source
📌 TL;DR
Extract specialized sub-agents once your prompt grows past a few hundred lines or your tool count exceeds a dozen.
Disadvantages
- Each new capability regresses the ones before it
- Costs balloon as every request carries a massive prompt
- Debugging the agent becomes archaeology — it’’s impossible to localize a failure