Sounds like a beautiful hallucination in the absence of getting the results into the message history (via Tool Message Output Node as Emilio explained).
Hint: I initially spent a lot of time “crafting” a nice message to the agent… until I realised that the agent receiving the output from Tool Message Output uses that information for its final response…
Since then I have become a little “lazier” and typically turn any table-based information into a JSON object via Table to JSON node and pass that to Tool Message Output… more than good enough for the agent in most cases ![]()