An assistant must schedule customer meetings from natural-language requests. The original design returned JSON with guessed time and timezone, then another service tried to convert that output into a booking action. Action-first design: when the system must execute, represent the operation as a tool with the smallest set of validated arguments required to perform it safely. The trap is stuffing context, guesses, and optional defaults into the tool call until the application can no longer tell what is genuinely required for a safe booking. Before A JSON blob with fields like preferred_time, customer_city, possible_timezone, and notes, followed by backend guesswork…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in