{"version":"2.1.314","anchor":"citations-on-tool-schemas-are-now-an-explicit-parameter-inst","canonical_anchor":"citations-on-tool-schemas-are-now-an-explicit-parameter-inst","heading":"Citations in tool definitions are now decided per request","tier":"internal","area":"API Requests","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/citations-on-tool-schemas-are-now-an-explicit-parameter-inst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Citations in tool definitions are now decided per request\n\nWhether the citations field is kept in tool definitions is now decided by each request instead of one global check\n\n**What**\n\nBefore sending tool definitions to the model, Claude Code removes fields that are not supported. It used to remove the citations field based on one global check. Each request now passes in whether to keep it.\n\n**Why**\n\nWhether citations are sent can now differ from one request to the next.\n\n- Area: API Requests\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}