Idempotency is an important attribute for correctness. Yep, you can document that POSTing to $ENDPOINT is idempotent, but you can't communicate that to caching layers throughout the network. QUERY, by definition, is idempotent and cacheable.
Does anyone know if this approach works at significantly larger scales? Curious about where it breaks down.
Great point. I wish more people realized that intuitively.