But some points are a stretch and that weakens the whole argument.
Point 3.1 : you waste HOURS of time debugging the wrong piece of code -- going off on a quest based on just one single chat message with incomplete info (and not even a stack trace as you deem it so essential yourself)? You don't ask any clarifying questions to validate your assumptions before sinking hours into work? Is that not your fault instead?
Point 4: so you want a whole IT support ticket (with attachments and priority classification if IM allows it) in a single chat message?
Why are you accepting support requests on chat instead of via a ticketing tool that keeps track of request volumes, history, SLAs etc.
If your workplace doesn't care about this level of productivity management and efficiency anyway -- why bother with these rules of engagement.
Also when someone pings you about an issue ... there is a chance you already know about an outage/issue and are working on it...and might just say "I know, fix is on the way by EoD, sit tight." If so... the whole stack trace and explanation of the problem scenario, what they have tried etc is all useless waste. They are just trying to optimize THEIR productivity by pinging you first instead. Two people can play this game.