Mixing Everybody's good ideas into one answer for your situation: Little real-estate on a device with no hover capability.
User @Evil Closet Monkey was on the right track: why isn't it obvious? Good design involves minimizing "cognitive load", so as a general rule you should ask yourself why it's not already obvious to the user. More specifically:
If there's enough room,
the best bet is probably repeating the details right next to the button as @maxathousand suggested. Place it above the button so they must see it before the button even after scrolling.
If you can't fit the explanation near the button,
but you've explained it elsewhere, you must not be allowing the screen to scroll (otherwise, you DO have space - just let it scroll more). In that case, both the button and the original explanation will be on-screen at the same time. Draw attention to that explanation (e.g., make it red and add the appropriate aria attributes) when it's not yet met.
If you don't have enough room explain the requirement even once, there's not much you can do. You probably need to make a more significant change to the overall flow.
In any case,
I strongly recommend the premise given by @knallfrosch: don't even disable the button! Let the user press it if they think they can. From there, you can take further steps to draw user attention to the problem. You can hide the error message or keep it un-emphasized, then make it extra obvious once they have clicked the button.