{"version":"2.1.277","anchor":"tool-call-validation-errors-now-include-custom-zod-issue-mes","canonical_anchor":"tool-call-validation-errors-now-include-custom-zod-issue-mes","heading":"Tool-call validation errors now include custom Zod issue messages","tier":"notice","area":"Tool Validation","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277\/e\/tool-call-validation-errors-now-include-custom-zod-issue-mes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.277","markdown":"### Tool-call validation errors now include custom Zod issue messages\n\nTool-call error messages now include specific custom validation messages from Zod\n\n**What**\n\nWhen a tool call fails validation, Claude Code builds an error message describing what went wrong, such as missing, unexpected, or wrong-type parameters. That message now also includes any custom validation error messages produced by the validation library (Zod) when a check is specifically marked as \"custom\".\n\n**Why**\n\nThis surfaces more specific, tool-author-written explanations of why a call failed, instead of only generic parameter-shape errors.\n\n- Area: Tool Validation\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}