For debuggability and to differentiate between moveChunk commands that are actually doing work from ones that are waiting for another moveChunk command to complete. One possible way to do this is to use CurOp::setMessage_inlock.