How do you review a software design paper when the code is not shared?

I keep getting asked to review software design papers where the design claims rest on code or prototypes that aren't available to reviewers.

It makes it hard to judge whether the design actually works as described.

How do you handle this in your own reviews, and what would you want authors to provide?