Why do workflow tools need to return JSON and TEXT two same results?

[swingchen01]

Self Checks

• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [X] Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Workflow tools return JSON and TEXT two same results, are there any special scenarios to consider? This will cause the FunctionCallAgentRunner to provide the duplicate tool results to the LLM"s API, which will take up twice the number of tokens.

2. Additional context or comments

If two same result is no special purpose, this logic will bring more performance consumption, more token consumption and fees, and more LLM context occupation

3. Can you help us with this feature?

• [X] I am interested in contributing to this feature.

[dosubot[bot]]

I found two similar discussions regarding the issue of workflow tools returning duplicate results in JSON and TEXT formats:

1. Why do workflow tools need to return two identical results? One is JSON, and the other is TEXT, which is currently unsolved and was last updated on November 9, 2024 ^[1].

2. How to resolve the issue where the agent tool invocation returns duplicate response content, which is also unsolved and was last updated on September 9, 2024 ^[2].

These discussions might provide additional insights or context regarding the rationale behind this design choice and any potential solutions or workarounds.

To continue talking to Dosu, mention @dosu.