The most useless type of call is one which requires no conscious thought by the speaker, as in “confirmed” or merely parroting what the other crew member has said. These were eliminated in the 1980s in my airline.
I really dislike responses such as "Previously Briefed," "Considered," or "As required." These really mean nothing.
Too often, however, I've heard crewmembers rattle off something merely because it's on the checklist. "Considered."
Well, after you got done considering it, what did you decide to do, and when are you planning on sharing it with the rest of us?
The most useful product of standardized calls and checks I've found is when I have caught myself thinking aloud, "Damn, how did I miss that?", to be followed up by another crewmember replying "that's why we have a checklist and three of us." It may be a small thing, but again, there's a reason certain items have more than one call, certain items require confirmation, certain items are included in a checklist and a procedure.
No, it doesn't enhance safety one iota when the calls are made with complete disregard to actual conditions. Clearly a "stable" call at 500' when the aircraft is well outside the published parameters is not only in error, but dangerous...and an outright lie. However, clearly that wasn't a standard call...because it didn't match the situation, and the standard call is required to describe the actual situation (we don't call the FAF over the MAP...we call it over the FAF, and we don't call "stable"--or whatever the standard call for a given operator may be--if we're not stable). Accordingly, an example of a "stable" call when the aircraft isn't stable doesn't condemn standardization or standard calls and procedures...just the pilot who makes the call in error.