Knowing how the tool was built isn't the issue; knowing what it does
Is the "operators provide context to their operands" pattern of thought really what all programmers are doing when they program in Perl, or is it something perl does for them so they don't have to worry about it?
The former. Programming is arranging operators to do what you want and return what other operators need. If that's not what you (generic, not any specific individual) do when you program, you're just making stuff up and hoping it does what you want. And we see a lot of that here, and that's really the core of why I think the least specific model is worth challenging.