when dont you consider sharding for writes?

we've been dealing with more and more write loads on our main database, and read performance is still fine. I've seen the advice about not sharding just for reads, but i'm wondering about the tipping point for writes. At what point does sharding actually solve write scaling issues, and what are the common pitfalls to watch out for when doing it for write-heavy workloads