{"version":"2.1.219","anchor":"tools-can-opt-out-of-the-aggregate-tool-result-budget","canonical_anchor":"tools-can-opt-out-of-the-aggregate-tool-result-budget","heading":"Tools can opt out of the aggregate tool-result budget","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/tools-can-opt-out-of-the-aggregate-tool-result-budget","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### Tools can opt out of the aggregate tool-result budget\n\nIndividual tools can now skip the shared output size budget and just use the hard ceiling.\n\n**What**\n\nA tool definition can now declare that its output is not subject to the shared tool-result budget lookup.\n\n**Details**\n\n- The tool-result size limiter takes a new fourth argument; when set it clamps straight to the ceiling instead of consulting the per-tool remote-config override.\n- The caller passes `e.skipAggregateToolResultBudget === !0` from the tool definition, so the behaviour is gated per tool.\n\n**Evidence**\n\n`skipAggregateToolResultBudget`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}