Aside from a visual paradigm which many have already proposed in this thread, I would also pay attention to anchoring. Give the user a baseline either in the manner of an example (i.e., this task is harder than task X but easier than task Y) or something more general like time to finish (similar to how recipes typically have a time to prep and time to cook stat).
I absolutely agree; that's something that users will learn as a part of onboarding and ideally will be clear once the rating has been displayed (if they see the number 2 they get a description of what a 2 is)
Aside from a visual paradigm which many have already proposed in this thread, I would also pay attention to anchoring. Give the user a baseline either in the manner of an example (i.e., this task is harder than task X but easier than task Y) or something more general like time to finish (similar to how recipes typically have a time to prep and time to cook stat).