yes I see your point, it just feels inconsistent somehow, as named parameters are nicely self-documenting, could be used to generate docs etc, but that's probably just a foolish consistency. In your example you could be cute and have something like:
protagonist.throw(a: => potato, :at => zombie, :force => 3)
which would be just as nice. But I'm sure there are places where this will be useful/necessary, in your chained example with single args it feels forced to have to name them.
On the other hand, the optional parameters are totally obscure, and need to be named.
Similarly:
The two unnamed parameters here are the things being join_in_matrimony'ed.In other words: unnamed parameters are for direct objects, named parameters are for adjectives and prepositions.
Although arguably the Rubyish thing to do with prepositions is chain them: