How do you review a software engineering paper when the code isn't shared?

I increasingly get asked to review papers that describe a new tool or technique but provide no artifact, and I'm never sure how much weight to give the claims.

I don't want to reject solid work just because the authors couldn't release code, but I also can't verify much.

How do you handle this in your own reviews, and what do you ask authors for?