Dynamic Multimodal Function Routing Protocol Rollout
Announce and explain a dynamic tool-routing agent architecture for multimodal image transformations via email.
Use this template to brief product and engineering stakeholders on a newly deployed dynamic routing function that selects between inpainting, upscaling, and prompt expansion tools based on user intent and token costs.
Role: Senior Agentic Workflow Specialist and Multimodal Automation Lead.
Context
- Business Unit: {{product_unit}}
- Router Core LLM: {{multimodal_router_model}}
- Connected Tools: {{target_image_endpoints}}
- Cost Ceiling: {{token_cost_threshold}}
- Routing Logic: {{routing_decision_criteria}}
- Target Launch: {{deployment_date}}
Task
Generate an operational launch email introducing the dynamic function-calling router powered by {{multimodal_router_model}} to {{product_unit}}, explaining how it automatically dispatches prompts across {{target_image_endpoints}} while respecting {{token_cost_threshold}} before {{deployment_date}}.
Method
- Articulate the strategic purpose of intelligent tool routing for {{product_unit}} in the email intro.
- Describe how {{multimodal_router_model}} interprets user multimodal inputs (image + text) to choose appropriate tools.
- Detail the routing matrix across {{target_image_endpoints}} (e.g., text-to-image vs inpaint vs controlnet).
- Highlight how {{routing_decision_criteria}} optimizes output quality against execution speed.
- Specify the automated guardrails that prevent exceeding {{token_cost_threshold}} per transaction.
- Outline the deployment schedule culminating on {{deployment_date}} and required stakeholder sign-offs.
Constraints
- MUST write in email format with clear organizational hierarchy and executive readability.
- MUST NOT exceed 500 words in total length.
- Ensure technical routing rules are understandable to both product managers and developers.
- Clearly state cost governance mechanisms tied to {{token_cost_threshold}}.
Output format
An email composed of:
- Subject: Operational Launch: Multimodal Function Router (Go-Live: {{deployment_date}})
- Overview & Business Value (2-3 sentences)
- Tool Routing Matrix & Criteria (Structured summary of {{target_image_endpoints}} and {{routing_decision_criteria}})
- Cost & Safety Guardrails (Bullet points on {{token_cost_threshold}})
- Timeline & Next Steps (Numbered milestone list)
Self-review
- Did I clearly explain how {{multimodal_router_model}} decides which endpoint to call?
- Are cost constraints under {{token_cost_threshold}} prominently featured?
- Is the deployment date ({{deployment_date}}) confirmed in the schedule?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.