People often argue about code readability. Some say it's subjective and there is certainly a degree of truth in that. But at the same time there is a large set of "best practices" out there that most engineers can agree on.
Which implies that there is some underlying objective factor we think of when we're talking about readability.
Here I propose a framework of thinking about it from the computational perspective. It explores computational effort required to understand a given code snippet and how common best practices tend to reduce it.
modelling is part of understanding. if the code you see is misleading and causes you to build incomplete models
In computational terms - the name of the entity is the key you'd use to find it within its scope. If the scope is small - a shorter name is sufficient to identify the entity unambiguously. With the larger scope - you have a large number of elements, and so the entity name needs to contain more information.