{"version":"2.1.295","anchor":"tengu-structured-output-strict-still-gates-strict-tool-schem","canonical_anchor":"tengu-structured-output-strict-still-gates-strict-tool-schem","heading":"No change to when tool definitions are made strict","tier":"internal","area":"Tools","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/tengu-structured-output-strict-still-gates-strict-tool-schem","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### No change to when tool definitions are made strict\n\nTool definitions are still made strict only when a remote switch is on, which falls back to off\n\n**What**\n\nNothing changes in how this works. Tool definitions are only made strict when the remote switch `tengu_structured_output_strict` is on, and it falls back to off when the server sends nothing. The server returned off both for this site's account and for an anonymous account; no reading has been taken under this release yet.\n\n**Why**\n\nThis is context only. You should see no difference.\n\n- Flag `tengu_structured_output_strict`: Off in both readings (read for one account on one subscription tier against v2.1.295; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}