Unverified50% confidenceCautionExact time
When using tools, the reasoning_content of every assistant turn in the history must be passed back verbatim (including turns where no tool call was initiated), otherwise an HTTP 400 is returned; when tools are not used, this field is ignored.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedDue to the stateless design of large model APIs, the entire tools array must be resent in every request, alongside the system prompt and conversation history.67% similarUnverifiedThe scope of forced tool calling (tool_choice) is a single generation (completion) rather than the entire session, so it must be re-specified on every call to the model.67% similarUnverifiedIf no parameters are explicitly passed in, the tool generated by as_tool will accept a text field named input by default66% similarUnverifiedIn agent pipelines, API tools more often return HTTP 200 OK with empty results or deprecated fields in the body, and conversational executors tend to fill gaps with parameter guesses rather than throw exceptions.66% similarUnverifiedThe fetch tools of assistant-type products usually allow only the GET method, and some tools can even only open URLs that have already appeared in the conversation, unable to initiate write operations such as POST or PUT.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1069331API
curl https://kongchang.com/api/v1/knowledge/claims/1069331MCP
get_claim(id=1069331)