The context gap in AI data access

A database schema tells an agent that a column named "amt" exists in a table called "txn_detail" with type DECIMAL(12,2). It does not tell the agent that "amt" represents gross transaction amount in cents, that it includes tax, that it should be divided by 100 for display, that it was renamed from "total_amount" in Q3 2025, or that the finance team considers it deprecated in favor of "net_amt" for revenue reporting.

Without this context, the agent will use "amt" in queries where "net_amt" is correct. It will format the value in dollars instead of cents. It will join on tables that have been superseded. The queries will execute successfully and return plausible results. The results will be wrong.

This is not a prompting problem. More sophisticated prompts do not compensate for missing business context. Retrieval-augmented generation helps only when the relevant documentation exists, is current, and is retrievable. In most enterprises, it is none of these things. The business context lives in the heads of experienced team members who learned it through years of working with the data.

Semantic enrichment delivers business context at the protocol level, before the agent makes decisions about how to query. When an agent describes a table through a query engine, the enriched response includes not just the schema but also column descriptions, data owners, classification tags, glossary term mappings, deprecation warnings, data quality scores, upstream and downstream lineage, and active incidents.

This transforms the agent interaction from "here are the columns and their types" to "here are the columns, what they mean, who owns them, how they relate to business concepts, whether they are reliable, and what you should watch out for." The agent receives in a single response what would otherwise require four or more separate tool calls to a catalog, a quality monitoring system, an ownership registry, and a lineage tracker.

The consolidation is not just convenient. It is architecturally important. Every additional tool call consumes tokens, increases latency, introduces failure modes, and requires the agent to synthesize information from disparate sources. A single enriched response eliminates these costs while ensuring the agent always has complete context.

Bidirectional cross-enrichment is the mechanism that makes semantic enrichment practical at scale. When an agent queries through a SQL engine, metadata from the catalog is included in the response. When an agent searches the catalog, availability information from the query engine is included in the results. When an agent inspects an object in storage, catalog metadata about that object is included. Each service enriches responses from the others.

This approach is fundamentally different from expecting agents to call multiple services and correlate the results. Correlation requires the agent to understand the relationship between services, to know which catalog entity corresponds to which query engine table, and to handle the case where metadata exists in one system but not another. Cross-enrichment handles all of this at the platform level, transparently.

The enrichment is session-aware. Once business context for a dataset has been provided in a conversation, it is not repeated in subsequent responses within the same session. This deduplication further reduces token consumption without sacrificing context quality.

The BIRD benchmark, designed specifically to evaluate text-to-SQL with external knowledge, demonstrates that models with access to business definitions, value descriptions, and domain knowledge significantly outperform models working from schema alone. The benchmark includes 12,751 question-SQL pairs across 95 databases with explicit knowledge evidence, making it one of the most rigorous tests of context-aware SQL generation.

Production architectures at scale reinforce this finding. Enterprise deployments that achieve reliable AI data access invariably include a semantic or context layer between the agent and the data. The specific implementation varies, but the architectural pattern is consistent: raw schema access produces unreliable results; contextually enriched access produces trustworthy ones.

The market is recognizing this pattern. Catalog vendors, semantic layer vendors, and query engine vendors are all adding context delivery mechanisms. The question is not whether context is necessary but how it should be delivered. The most efficient approach is enrichment at the protocol level: every response enriched automatically, no additional tool calls required, no agent-side correlation logic needed.

An inaccurate query that executes successfully is more dangerous than one that fails. A failed query surfaces an error. An inaccurate query surfaces plausible-looking numbers that may inform decisions before anyone realizes they are wrong. In regulated industries, inaccurate data access can trigger compliance violations. In financial services, it can produce incorrect risk calculations. In healthcare, it can lead to flawed analyses of patient outcomes.

The context gap compounds over time. Agents that generate inaccurate queries erode trust in AI-powered data access. Teams that lose trust in the results revert to manual processes, negating the investment in AI infrastructure. Gartner predicts that 50 percent of AI agent deployment failures by 2030 will stem from insufficient governance runtime enforcement, a failure mode that is closely linked to the absence of business context at the point of query execution.

Closing the context gap is not a feature. It is the prerequisite for trustworthy AI data access. The solution is not a better model, a longer prompt, or a more sophisticated agent framework. It is better context, delivered automatically, at the protocol level, on every response.