I wouldn't be in favor of a programming language that tried to enforce verbalizability (I'm thinking something like basic here). But I do think that having a program "tell a story" is a boon for comprehension. Have operations, variable names, function names, choice of where and when to use a function, etc be in such a way to optimize the narrative quality of the code. But I don't immediately see a way for the language construction itself to benefit here. I think having clear structural code is a boon to quickly scanning and understanding the structure of code.
It's also probably more productive for that purpose than almost anything else. Why? Availability of tools, and also fitness for use. You usually don't really want to be using Python, say, in that environment, because you don't want to have to burn an interpreter onto your device, and you don't want the runtime inefficiency, and and and...
A while ago I started writing something about meter in programming languages; what could we gain by thinking not just about making them look more like English but more able to be read aloud? I didn't come to any useful conclusions, but I do note that of all the unpronouncable symbols we use the semantic whitespace of python is the most difficult to convey adequately.