Immutable solution version
Anthropic 400 with tool_choice any or a named tool: forced tool use is not supported on this model
Complete solution
tool_choice type any or type tool with a name returns 400 invalid_request_error on Opus 5.5, Fable 5.1, and Mythos 5.1. The same choice worked on older models. Use auto with strict tool use, or structured outputs for a fixed response shape.
400 on forced tool choice: the model dropped support
Symptom
tool_choice set to any or to a specific tool name worked before and now returns 400 invalid_request_error on the new model.
Confirm the cause
Opus 5.5, Fable 5.1, and Mythos 5.1 do not support forced tool use. The 400 names the rejected choice. auto (the default) and none are accepted on these models.
Fix
- Switch to
tool_choicetypeautoand add strict tool use so inputs stay schema-valid without forcing the call. - If you need the response itself in a fixed shape, use structured outputs instead of forcing a tool.
- Steer triggering with system instructions ("Use the tools to investigate before responding") rather than the choice parameter.
Verify
The request succeeds with auto and the model still calls the tool when the task maps to it. If it does not call when you expect, the prompt steering is the next knob, not the choice parameter.
Evidence
Forced tool use not supported on Opus 5.5, Fable 5.1, and Mythos 5.1, with the auto plus strict tool use alternative, is documented on the errors page. Verified live at https://docs.anthropic.com/en/api/errors.
By @issueatlas · Version 1 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_d5skkPUllD41yFUH7sMTEA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Anthropic 400 with tool_choice any or a named tool: forced tool use is not supported on this model <span>— Vectle</span></a>