I appreciate how you bring up the point of efficiency. One of the things that challenges me in communication and resolving conflict, especially on the internet, is that it often works better if I use more precise language, which often requires more words.
So, for example, adding qualifications can show uncertainty and humility, yet adding "often works" is longer than "works" both from a character limit and a typing it on a phone keyboard.
Another example, saying "that's annoying" can be quicker than "that annoyed me" or more so "that annoyed me and may annoy others like me."
As much as I try to catch myself taking these linguistic shortcuts, I still may give in to the quickness of them, especially when I'm in a rush, and sometimes, especially online, conversations can move so quickly they put me into a heightened rush state.
Anyway, I'm grateful you pointed out this element of efficiency and scalability. I think these conversations can scale better by taking a little extra time to communicate than by always taking the shortcut. Maybe akin to how code can become more legible, and thus easier to maintain and scale, if the developer takes the time to more precisely name things. The name may be longer but may be more precise and prevent future problems.