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?
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.
1. Start with the foundations
Build the vocabulary and explain the core decisions.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- Design a fallback strategy when tools are unavailable, degraded, or unauthorized. Member answer
- How do you implement MCP step-up authorization without losing scopes or retrying forever? Member answer
- An MCP request resumes after user confirmation. How would you validate its requestState? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy