Tool Schema Migration Notice Spec

Role: Enterprise Agent Platform Technical Account Lead

Context

• Client engineering account: {{client_account}}
• Deprecated tool signature: {{deprecated_tool_definition}}
• Updated tool schema specification: {{replacement_tool_schema}}
• Strict migration deadline: {{migration_window_date}}
• Impacted autonomous workflows: {{affected_workflow_chains}}
• Staging sandbox URL: {{sandbox_testing_endpoint}}

Task

Generate a developer-oriented client notification email specification outlining breaking tool schema changes, providing explicit JSON schema diffs, and delivering migration instructions to prevent agent execution failures.

Method

1. Parse the structural breaking changes between {{deprecated_tool_definition}} and {{replacement_tool_schema}}.
2. Identify specific operational failure risks across {{affected_workflow_chains}} if migration is missed.
3. Establish the timeline of deprecation phases culminating on {{migration_window_date}}.
4. Draft a direct, developer-ready email copy explaining the JSON schema update rationale.
5. Include step-by-step validation instructions for {{sandbox_testing_endpoint}}.
6. Formulate proactive mitigation steps to prevent agent hallucination on outdated schemas.
7. Specify direct escalation channels for schema validation support.

Constraints

• MUST include before-and-after JSON schema snippet blocks in the specification.
• MUST NOT use vague deprecation dates; anchor everything to {{migration_window_date}}.
• Email draft body MUST stay between 250 and 350 words.
• Emphasize zero-downtime hot-swapping procedures.
• Language MUST be precise and targeted toward API developers.

Output format

Provide the specification in three numbered markdown sections:

1. Technical Broadcast Header (Subject lines, target developer audience, urgency rating)
2. Migration Specification Email (Context, schema diff, sandbox instructions)
3. Testing Checklist & Failure Mode Reference (Verification queries, failure signatures)

Self-review

• Validate that {{deprecated_tool_definition}} and {{replacement_tool_schema}} are contrasted clearly.
• Check that the sandbox verification steps on {{sandbox_testing_endpoint}} are functional.
• Ensure all constraint limits on length and formatting are strictly satisfied.