{"version":"2.1.295","anchor":"tool-creation-can-strip-result-data-via-stripforcreation","canonical_anchor":"tool-creation-can-strip-result-data-via-stripforcreation","heading":"Tools can now trim their results before Claude sees them","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/tool-creation-can-strip-result-data-via-stripforcreation","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Tools can now trim their results before Claude sees them\n\nA tool can now strip parts of its result before the result is turned into the message passed back to Claude\n\n**Unclear.** It is not known which tools use this step, so it is unclear which results are affected.\n\n**What**\n\nA tool call is one action Claude takes, such as reading a file or running a command. When a tool finishes, its result is turned into a message for Claude. A tool can now run its own optional step first that strips parts of the result. Tools that don't have this step behave as before.\n\n**Why**\n\nThis could make some tool results smaller in what is stored or sent to Claude.\n\n- Area: Tools\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}