.Net: Bug: Invoking a tool call without ID then following up with another chat completion message throws null pointer

[gjz22]

Am not sure whether this is a bug or a feature request.

Describe the bug
The normal way OpenAI tool calling is performed is [key information in brackets]:

1. We pass a prompt and a list of tools to OpenAI
2. Open AI responds with a tool call [with a tool call id]
3. The tool call is invoked by the application
4. We pass the result of the invocation as a chat content back to Open AI [With the ID]
5. Open AI passes back
   However, if you invoke a tool directly (starting from step 3 above with a synthetic invocation constructed by the app: new FunctionCallContent(myFunction, myPlugin, null, myArguments)) there is no id from Open AI, so there is no id. When constructing the OpenAI tool call object this throws an error that the toolCallId can not be null.

To Reproduce
Steps to reproduce the behavior:

1. Invoke a tool call (FunctionCallContent) with a null id
2. Get the function result
3. pass to another chat completion service call
4. Get an argument exception

Expected behavior
I'd expect one of two things to happen:

1. [preferable] A better way to pass results of these synthetic methods back to OpenAI for processing
2. A clear error that either results from synthetic executions are not supported in the ToChatMessage

Platform

• Language: C#