Describe the problem this hire has to solve
Most job descriptions list duties. The more useful question is why you are hiring now: to replace someone who did the job well, to grow a team, or to fix something that is not working. Those are three different searches, even when the title is the same.
A candidate who has already solved a problem like yours is worth more than one who matches every bullet point. We can only find that person if we know what the problem is, so tell us plainly what you need them to get done in their first year.
Separate what is required from what is preferred
Each requirement you add shrinks the pool. Name the two or three things a person cannot succeed without, and treat the rest as a bonus. The test for any requirement is whether you would turn down an otherwise excellent candidate who lacked it.
Settling this early saves weeks, because the alternative is learning what you really need by rejecting the first short list. It also keeps strong people with unconventional backgrounds from being screened out before you ever see them.
Be honest about the hard parts
Every role has them: a demanding boss, a team with recent turnover, a heavy travel schedule. Put them in the brief, even those you would never advertise. Candidates find out eventually, and finding out late often ends in a declined offer or an early resignation. The ones who know up front and still want the job are the ones who stay.
Know your interview process before you start
Decide who needs to meet the candidate, in what order, and who makes the final call. Have the compensation range approved and interview time set aside. Good candidates usually have other conversations going, and a long gap between interviews is often when one of those becomes an offer. A clear process and prompt decisions also show them what working for you is like.