You might try to update Keep to see if they cleaned up some of the unnecessary syncing. But those partial wake locks shouldn't be a huge issue, depending on when they happen.
It's hard to explain, but the best behaved apps (most Google apps) will try to time their syncing for when you have a lot of battery and/or are on WiFi
Many will also try to batch the syncs together. So if the phone is woken up by say the maps app, other Google apps will piggy back on that connection before your radio goes back into low power, then sleep state.
However Keep is new, and may have been rushed or not as polished. I might try updating it.
SyncAdapters are complicated to program and are often added as a refinement to an app after release. SyncAdapters are how they do those battery saving tricks for network usage.
Partial Wake Locks by themselves are not generally harmful unless they are spaced out in such a way as to keep the radio from falling back into low power mode. Partial wake locks only keep the CPU on, not the screen.
http://developer.android.com/reference/android/os/PowerManager.html
In case you are curious here's a video about how it works:
https://developers.google.com/live/shows/915123505
Edit:
What worries me more is that VZW MMS thing, not sure why that is keeping your CPU on for such a long period of time. 24 minutes? That seems very badly behaved.