Because the rules are different for methods that have multiple parameters on a side than for methods with a single parameter on a side.
Ignore these two methods for a moment and think about methods in general.
If a method has only one output, we allow it to just be the same as the name of the function because it is obvious what that output is -- the only thing it could possibly be.
If a method has zero outputs and only one input, we allow that input to be the name of the method (though most of those are actually properties, not methods).
But if it has multiple inputs, one of those gets to be the name only if the name of the method and the name of the parameter are exact matches, which pretty much never happens.
When you apply those rules to these two methods, you get the current behavior.
It might be if we had never shipped those functions before. I do not think it is a good tradeoff to modify those functions at this point. Even deprecating them and creating new functions doesn't seem like a particularly useful fix up to me. But if it got enough kudos from community, I'd support doing it.
Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.