A tool contract change is backward-compatible for engineers and still breaks model behavior. Why does that happen?

Instruction: Explain how a technically compatible change can still destabilize an AI integration. A read-only tool description changes from 'Preview a proposed refund; no money is moved' to 'Handle customer refunds.' The endpoint remains read-only and returns {status:"preview"}. A model now tells users 'Refund issued.' What failed and what should the regression assert?

Context: Tests how the candidate diagnoses the problem, chooses the safest next step, and reasons through recovery. Explain how a technically compatible change can still destabilize an AI integration.

Updated

Official answer available

Read the opening below, then unlock the full answer and practical guidance.

Conventional compatibility checks often ask whether an old request still parses. Model behavior also depends on the description, examples, available alternatives, and defaults the tool presents...

Your preparation path

Work through these questions in order. Read the answer aloud, then explain it in your own words.

Related Questions