My opinion is: by the time you've accurately described the task to the AI, and confirmed all the details, you may as well have done the thing yourself.
Having to write/speak the assembly language of each component of that every time in chat is not going to win in the market.
I don't see these statements as "assembly language", they are questions a human assistant would ask as well.
“There’s a court available 150 miles away; the Uber will be at your door at 3PM to get you to the court by 6” is a legal but non-sensical solution in your version of the interaction.
You have to have some kind of implicit rules and some kind of explicit configuration whether that’s “when I say my door, I mean X” or “when I play tennis, the default duration is an hour and I prefer club Y over town court T1 over town court T2.” And an implicit “people don’t want to spent more time in transit than at an activity, so first constrain search and issue a notice to the user if a solution chosen violates this”.
Looking at how we might approach your tennis court scenario I see a lot of mistakes that the AI could make. Maybe the court is members only, but it didn't realize the court is inside a gym or location where a human would be sure to check that. Or it finds one an hour away, so your Uber is expensive.
I assume if you do this often, you'd know about potential tennis courts in the area. So for me I'd rather do the research up front myself, but this could be personal preference. In the end, maybe we have to see how good these `AI + some code` apps get, but I wouldn't want to use the first versions.