[x] Name your Pull Request title clearly, concisely, and prefixed with the name of the primarily affected package you changed according to Good commit messages (such as memory: add interfaces for X, Y or util: add whizzbang helpers).
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. Fixes #123).
[x] Describes the source of new concepts.
[x] References existing implementations as appropriate.
I noticed that after the recent addition of ToolCalls support，it is no longer effective to use the tool with the openai agent. This is because after obtaining the openai results for the first time, the tool was called, but the next request to call openai could not be correctly formed, resulting in empty response. I improved each request and solved the problem
When running the TestExecutorWithOpenAIFunctionAgent in the executor_test.go directory of the agent, both tools will return an empty response, and the result can now be returned correctly
PR Checklist
memory: add interfaces for X, Yorutil: add whizzbang helpers).Fixes #123).golangci-lintchecks.I noticed that after the recent addition of ToolCalls support，it is no longer effective to use the tool with the openai agent. This is because after obtaining the openai results for the first time, the tool was called, but the next request to call openai could not be correctly formed, resulting in empty response. I improved each request and solved the problem
When running the TestExecutorWithOpenAIFunctionAgent in the executor_test.go directory of the agent, both tools will return an empty response, and the result can now be returned correctly