{"version":"2.1.323","anchor":"tool-input-json-parse-failures-get-a-dedicated-error-with-hi","canonical_anchor":"tool-input-json-parse-failures-get-a-dedicated-error-with-hi","heading":"Clearer error when a tool call's input is not valid JSON","tier":"notice","area":"Tool Calls","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/tool-input-json-parse-failures-get-a-dedicated-error-with-hi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clearer error when a tool call's input is not valid JSON\n\nWhen a tool call's input cannot be read as JSON, the error now lists common causes such as unescaped backslashes in file paths\n\n**What**\n\nWhen Claude uses a tool, it sends the tool its input as JSON, a structured text format. When that input cannot be read, the error message now lists common causes:\n\n- Unescaped backslashes in file paths\n\n- Control characters in the text\n\n- Output that was cut off before it finished\n\n**Why**\n\nThe more specific message gives the model a better chance to spot what went wrong and send a corrected tool call.\n\n- Area: Tool Calls\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}