Genie works better with data descriptions than long instructions
A Genie space can let a team ask sales and pipeline questions in plain English instead of waiting for someone to write SQL by hand. The biggest improvement does not come from writing long free-text instructions. The model understands the data better when each fact is placed where it belongs.
Table and column ions should come first, followed by a small set of strong question-and-SQL examples. Join relationships should be declared clearly, including how many records usually relate to each other. Free-text instructions should be saved for information that has no structured place.
Wrong answers are better fixed at the layer than by adding more instruction text. A small with questions and expected SQL should be tested after every change.
Key points
- Long free-text instructions are not the best main tool for teaching Genie about data.
- Table and column ions should be added before broad instruction text.
- A few curated question-and-SQL examples can help more than extra prose.
- Join relationships and should be declared clearly.
- A small of questions and expected SQL helps catch after changes.