Design tool parameters by separating required arguments, optional context, and unsafe ambiguity.
The situation Your team wants a schedule_followup tool. The proposed arguments include free-text rationale, sales-stage notes, a guessed timezone, suggested email copy, and an optional owner identifier that the backend may or may not override. The same model can require different contracts depending on what happens after generation. The framework Consumer → Contract → Action Ask who consumes the output, what drift would break, and whether the system needs to execute an operation instead of merely describe one. Shortcut to avoid Choosing one output style for every workflow because it feels simpler. The stronger the machine dependency, the more explicit…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in