You can achieve number 1 (managing user expectations) most simply by just stating any restrictions that exist. You don't need to state "also you can't break these other laws or do other things we may think are naughty" - that's not managing expectations, that's just intimidation.

I'd **love** for the ToS to be an opportunity to break out of the legal-ese and signal to people that a new font of data has been constructed for public use -- that's why I [submitted a non-ToS ToS](https://github.com/GSA/API-Resources/pull/4). Maybe if that was the base, and the agency had no legal levers in any way, it'd be easier to have an agency jocularly wag their finger at the user and remind them to be nice.

But what we're dealing with here is a contract, and one of the ramifications of forcing citizens to sign one before accessing data is that it makes it dangerous for the agency to also say mushy, abuse-able things like "you shouldn't misrepresent the data or imply we endorse your claims". That's a recipe for cracking down on parody and criticism the agency finds uncomfortable.