Design a migration plan for tool schema changes across many prompts and agents.

Instruction: Version model-facing and server contracts together, with compatibility checks and a rollback path for affected workflows.

Context: Migrate a tool schema without silently changing units, permissions, or default behavior for existing agents.

Updated

Official answer available

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

I would inventory every caller: prompts, agent configurations, parsers, approval screens, and background jobs. Then classify the change by behavior, not just JSON compatibility. Renaming a field, changing units, or adding a default can break an agent even when a conventional API client accepts it.

For a hypothetical...

Your preparation path

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

Related Questions