Ribbing aside, the "rethinking" here sounds a lot like an AI-specific spin on the "bring the code to the data, instead of data to the code" paradigm. I imagine that the same multitenancy caveats of allowing arbitrary user-defined queries against a relational database (execution limits, access controls, etc.) will apply here as well.
Maybe this is just different from web search, but it seems like the model needs sequential tool calls to know where to look next, and coding agents have already put in a lot of work to encourage parallel tool calling.
This approach usually works great but I can see many use cases where a smarter search strategy may make sense especially to optimize context.
(Your earlier comments were, of course, fine.)
Normally you'd tell your customer they need to fix their code if they're doing something inefficient, but here, they didn't write the code and are presumably not expected to understand it.
