There are wildly different opinions about how useful/effective these tools are, despite the fact that they generate tens of millions of dollars of revenue and arm a significant percentage of all web app testers (we've banned them at Matasano, for whatever that's worth).
HN usually doesn't care about inside-baseball appsec stories, but I think there's an opportunity for HN to geek out on the big unsolved problems Zalewski --- one of Google's leading security people --- suggests afflicts the space:
* How do you compare HTTP/HTML responses to detect templated versions of the same basic page structure (pages that differ only in the database row used to generate them, but with the same inputs and the same mapping of inputs to outputs)?
* How do you even detect whether a page is valid or not? Most large web apps intercept and articulate the page-not-found exception, so that it looks like any other part of the app.
* How do you figure out how to reliably and automatically feed inputs to 100 different applications that will encode inputs totally differently?
* How can you distinguish a "500 Internal Server Error" caused by an uncaught exception handler in defensive code from a "500 Internal Server Error" caused by an undefended component crashing "exploitably"?
There's pretty good money in a simple, clever, effective answer to any subset of these questions, for what it's worth.