1. Stale data creates confident hallucinations.
Most enterprise integration pipelines are batch-oriented. Data gets pulled, transformed, and loaded on a schedule — hourly, daily, sometimes weekly. That was fine when a dashboard only needed to be approximately right. It's catastrophic when an agent uses that data to make decisions.
The agent doesn't know its data is old. It doesn't know to doubt itself. It reasons clearly from premises that stopped being true hours ago, then delivers a confident, well-formatted answer that happens to be wrong.
2. Tight coupling makes agents brittle.
Traditional integration layers often enforce strict contracts — a rigid schema that defines exactly what format data arrives in and what format it leaves in. Break the contract, and the integration breaks.
Agents are pattern-matchers, not rule-followers. They work best when they can flex, adapt, and handle variation. Force them into rigid API contracts designed for deterministic software, and every upstream change becomes an agent failure waiting to happen.
3. Latency destroys the decision loop.
Agents work in loops: perceive, reason, act, observe, repeat. That loop has to be fast. When data retrieval is slow — because it's traversing five middleware hops, waiting on a batch process, or hitting a rate-limited legacy API — the loop breaks. Agents time out. Context windows fill with waiting. Actions become stale before they execute.