A model deployment is updated. The existing agent still returns text, but tool arguments now frequently violate the expected contract. What should happen?

Published
  1. Run regression evaluation against tool schemas and representative tasks before promoting the change
  2. Change only the agent's display name
  3. Treat successful HTTP responses as full compatibility proof
  4. Disable schema checks permanently

Comments — 0