The bot can gather this restaurant specific information over several conversations with the restaurant. This wasn't possible before. This domain isn't too wide.
You are probably right that in principle one could eventually come up with a full catalog of features of a reservation. There would be about, say, 100 of those.
I seriously doubt that they will proceed to define and collect them, since those are probably 10% or less of all reservations, but lets say they would.
Then still, the conversation you make to make the reservation is a process in which you make the decision.
Say, there is a place inside at 20:00 or a place in the garden at 20:30. Are you going to let Google choose between the two options for you?
Do you imagine there would be an api in which you specify to the assistant, before it makes a call, your preferences in that much granularity?
I seriously doubt that they will proceed to define and collect them, since those are probably 10% or less of all reservations, but lets say they would.
Then still, the conversation you make to make the reservation is a process in which you make the decision.
Say, there is a place inside at 20:00 or a place in the garden at 20:30. Are you going to let Google choose between the two options for you?
Do you imagine there would be an api in which you specify to the assistant, before it makes a call, your preferences in that much granularity?