Tool Execution Failure Propagation and Latency Distribution Forecast
Forecast failure cascade rates, retry storm probabilities, and end-to-end response latency across autonomous tool pipelines.
Use this template when evaluating reliability and degradation risks in autonomous agent execution graphs. It simulates failure propagation across interdependent tool calls to optimize fault tolerance.
Role: Staff Reliability Engineer specializing in stochastic modeling and autonomous tool-calling architectures.
Context
- Workflow Graph Definition: {{workflow_dependency_graph}}
- Tool Reliability Baseline: {{tool_error_rates}}
- Configured Retry Policies: {{retry_policy_parameters}}
- Network Latency Telemetry: {{network_jitter_data}}
- System Target Threshold: {{sla_breach_threshold}}
- Load Spike Scenario: {{traffic_surge_multiplier}}
Task
Generate a probabilistic reliability forecast that quantifies failure propagation, retry amplification, and latency tail behavior across {{workflow_dependency_graph}} under the stress of {{traffic_surge_multiplier}}.
Method
- Translate {{workflow_dependency_graph}} into a directed acyclic graph (DAG) of state dependencies and external tool endpoints.
- Calibrate baseline node failure probabilities using the empirical metrics in {{tool_error_rates}}.
- Apply {{retry_policy_parameters}} to model exponential backoff, jitter, and secondary invocation amplification on failed calls.
- Superimpose {{network_jitter_data}} onto multi-agent turnarounds to build cumulative distribution functions for latency.
- Simulate the stress condition defined by {{traffic_surge_multiplier}} to identify cascading timeout loops.
- Calculate the overall likelihood of breaching {{sla_breach_threshold}} for end-to-end task completion.
- Pinpoint the top three critical failure points where single-tool degradations induce system-wide agent deadlocks.
- Provide concrete modifications to timeout configurations, circuit breakers, and fallback schemas.
Constraints
- MUST evaluate compound probability chains rather than analyzing tools in isolation.
- MUST NOT treat latency as a Gaussian distribution; tail latency (p95, p99) must be explicitly modeled.
- MUST quantify retry storm risks directly against downstream service limits.
- All suggested policy changes must preserve agentic autonomy without infinite loops.
Output format
Deliver an engineering analysis report containing:
- Reliability Forecast Summary (key probabilities of end-to-end completion vs failure)
- Failure Propagation Matrix (tabular mapping of tool nodes, isolated error rate, propagated error rate, and retry amplification)
- Latency Distribution Breakdown (p50, p90, p99 cumulative runtimes against {{sla_breach_threshold}})
- Circuit Breaker & Resilience Recommendations (exact parameter changes for timeouts and retries)
Self-review
- Did I trace how a failure in an upstream tool cascades into subsequent agent tool-selection steps?
- Are tail latencies accurately compounded across nested sub-agent calls?
- Does the analysis address the specific multiplier provided in {{traffic_surge_multiplier}}?
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.