Implicit takes are a convenience to players; in general, we would like to avoid asking players to type any more obvious commands than strictly necessary, while allowing the computer to guess as much as it safely can.
Occasionally, though, we have designed a timed puzzle in which the player has a limited number of moves in which to accomplish his objectives. In that case, the implicit take complicates matters, because it means that a player who types
gets away with a spare move compared to the precise but naïf dupe who types
…and really, that doesn't seem quite fair. The way to fix this problem is to fill in the extra minute on the clock during the implicit take; and that is indeed what we do in the following example.
Test me with "take crispy duck / eat crispy duck / eat steak pie".
You can see a crispy duck and a Guinness steak pie here.
> take crispy duck
> eat crispy duck
You eat the crispy duck. Not bad.
> eat steak pie
(first taking the Guinness steak pie)
You eat the Guinness steak pie. Not bad.