My opinion...
I like the idea of being helped not to make stupid mistakes. MXP was nice for shops to stop buying the wrong item by accident... but then again when someone enters the room as your clicking it scrolls... unfortunate if your visiting the weaver...
Had to make sure you weren't autoscrolling at the time for that one. I got into the habit of typing list <item name> but that's slow... maybe giving items a number is the easiest but silly looking suggestion to stop making mistakes.
As a software developer... I can see to implement this idea it would require a "new field" in the section storing the players items. I groan at such things... new fields equal new widespread crashing opportunities.
There is also another consideration... is the item kept, or is the item kept to the player? (ie, What happens if a kept item is given to another player?)
This would then lead onto other issues that would possibly cause problems...
keep black-crappie
eat black-crappie?
keep recall
recite recall splork?
There would develop cases where we want this command to do things differently depending on the item-type. Then they try and code for this and it can cause an effect like a tangled ball of twine.
If I got given this idea as a developer, I'd add it too my long term improvement list and forget about it. It's a positive idea, but it's to much effort for too little result.
I just bent my pocket knife the other day... wish I had "kept" it beforehand... you see sometimes life is just like this.