Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Error HandlingArea: what it touches
Internal ChangesKind: in v2.1.267,
Internal ChangesSection of the release
What
When Claude Code calls the API and gets back a 400 error whose message references tools.*.input_schema (or the custom-tool variant tools.*.custom.input_schema), it's now recognized and labeled as a tool_schema_invalid error, rather than being treated as a generic, unclassified 400 error.
Why
Giving this specific error its own classification makes it easier to identify that a tool's input schema is the actual problem, rather than having to dig through a generic error message to figure out what went wrong.
