This is an interesting topic to me, as well as @
CaptBill 's post.
Traditionally in systems training, it was all about counting rivets; items on a bus; temps, pressures and levels that trigger warnings.
In integrated airplanes, dealing with automation specifically, there is a large lack of training on logic and the interconnected processes of what you told it to do (lateral and vertical waypoints and the logic you programmed for to achieve that lnav/vnav, non-integrated modes, or hand-flown) and what you mentally expect it to do (stay at altitude prior to xx miles to start a decent, slow at xyz) and resolving those differences (did you fat finger the entries, is there a logic mode causing it to this, or is it broke and you need to hand fly).
Whether it's fatigue, complacency or ignorance, we need to make a decision and fly the airplane and comply with our lateral and vertical clearance.
Also, there are ways to mentally stay sharp like when you get the 50 mile visual to Springfield. Is the descent clearance going fit my overall descent profile to hit the marker in idle to that point? Does my mental math, and my expectations of the programmed performance agree with what it's actually doing?
tl;dr. Mode awareness, do I know what it's doing? If not, was it me or the machine?
Just some food for thought...