{"version":"2.1.267","anchor":"new-tool-schema-invalid-error-classification-for-400s-refere","canonical_anchor":"new-tool-schema-invalid-error-classification-for-400s-refere","heading":"New tool_schema_invalid error classification for 400s referencing tools.N.input_schema","tier":"internal","area":"Error Handling","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/new-tool-schema-invalid-error-classification-for-400s-refere","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### New tool_schema_invalid error classification for 400s referencing tools.N.input_schema\n\nAPI 400 errors about an invalid tool input schema now get their own error type instead of being generic\n\n**What**\n\nWhen 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.\n\n**Why**\n\nGiving 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.\n\n- Area: Error Handling\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}