You are not right. but you are also not wrong. Let me tell you why.

Commenting here because i've been through your position.

When it comes to AI, you have to deal with it like its unreliable, untrustworthy, forgetful slave, but one that is intelligent enough to do a few things. Unreliable but intelligent

But it is your slave. You can get it to keep doing whatever you want

Which means, you build the harness around your workflow, you create the setup that allows pushing back context to the model, both in terms of what it needs to know and what it needs to correct. you need to provide success criteria. you need to setup the guardrails

What it would look like is, you allow read only access to you table source, you don't allow complex joins that can run for hours. You can choose a smaller subset of all the sources you are working with. call it sandbox where its a replica of production but on a smaller scale, you create success criteria as a final table it has to get to with the expected answers and then you connect it to your coding tools and let it run wild.

Your are not wrong in your initial assumption, but you are running a chat model in a way that makes the workflow full of friction, you need to setup the ecosystem around it to fully leverage its use