๐ฏ๐ด% ๐ฏ๐ฒ๐๐๐ฒ๐ฟ ๐๐ ๐ฎ๐ฐ๐ฐ๐๐ฟ๐ฎ๐ฐ๐. ๐ก๐ผ ๐ป๐ฒ๐ ๐บ๐ผ๐ฑ๐ฒ๐น. ๐ก๐ผ ๐ป๐ฒ๐ ๐ฑ๐ฎ๐๐ฎ. ๐๐๐๐ ๐ฏ๐ฒ๐๐๐ฒ๐ฟ ๐ฐ๐ผ๐ป๐๐ฒ๐
๐.
Thatโs the headline from a controlled NL-to-SQL experiment discussed by Manoj Shanmugasundaram in Metadata Weekly. Across 522 query evaluations, the only variable that changed was context quality โ and it made all the difference.
Concise, high-signal context (business definitions, SQL patterns, domain rules) drove a 38% accuracy gain. Verbose, catalog-style documentation? Performance dropped and costs rose. More words diluted the signal.
The biggest lift wasn't on simple or extreme queries. It was on medium-complexity ones โ the joins and aggregations that make up everyday analytics work โ where focused context delivered a ๐ฎ.๐ญ๐ฑ๐
๐ถ๐บ๐ฝ๐ฟ๐ผ๐๐ฒ๐บ๐ฒ๐ป๐.
The mindset shift: metadata was built for humans to browse. Now it also needs to work for machines to reason. Most teams are still optimizing for readability, not machine usability.
If your "talk to data" initiative is stalling, it might not be a model problem. It might be a context problem.
Manoj breaks down what machine-usable context actually looks like โ and how to get started without rebuilding your stack.
Read it in Metadata Weekly:
https://metadataweekly.substack.com/p/the-context-problem-nobodys-fixing