alt Hacker News> could collide with alarm fatigue and the disengaged overseer problem
Depends both on the form the "alarm" takes as well as the false positive rate. If the alarm is simply being told to go around, and if that has the same authority as a human, then it's an inconvenience but there shouldn't be any fatigue. Just frustration at being required to do something unnecessary.
Assuming the false positive rate were something like 1 incident per day at a major airport I don't even think it would result in much frustration. We stop at red lights that aren't really necessary all the time.
Depending on how late the go-around/aborted landing is triggered, that can be a danger in itself. Any unexpected event in the landing flow has a risk, to the point that there's a "sterile cockpit" rule in that window.
Even if it's just a warning to the ATC, distracting them and forcing them to reexamine a false positive call interrupts their flow and airspace awareness. I get what you're saying, that we could err on the side of alert first, out of precaution; but all our proposed solutions would really come down to just how good the false positive and false negative rates are.
BTW, stopping at a red light unnecessarily (or by extension, gunning it to get through a yellow/red light) could get you rear ended or cause a collision. Hard breaking and hard acceleration events are both penalized by insurance driver trackers because of that.