Good, non-trivial, and RESTful -- pick two. REST doesn't define any sane way of reporting execution errors (and no, smashing errors in execution layer into transport layer, i.e. HTTP codes, is not a sane way).

The only good way to use REST is to use it as it was intended: for applications employing only trivial CRUD model. Trying anything above that calls for RPC.