WCF Data Services supports JSON out of the box, no need to add attributes or anything. In order to receive a response in JSON format clients use standard HTTP content type negotiation. Specifically, they need to include "application/json" in the "accept" header of the request. There are examples in this section of the OData protocol documentation:
http://www.odata.org/developers/protocols/operations#RetrievingfeedsEntriesandservicedocument
(those examples show the raw HTTP requests. different client HTTP APIs have different mechanisms to specify request headers)
The [JSONPSupportBehavior] attribute is an example of an extension that allows clients to use a URL query string option ($format=json) in addition to content-type negotiation, and also adds support for "JSONP" ($callback=[function-name]). These are useful in situations where you don't control the headers, such as when doing cross-domain access through script tags.
If you want to use the JSONPSupportBehavior you can obtain it here:
http://code.msdn.microsoft.com/DataServicesJSONP