The same retry would charge a customer twice. What must the tool support?
Why D is the answer
Idempotent calls
An idempotency key makes a repeat call safe.
In detail
- An idempotency key makes a repeat call safe.
- Retries happen, so plan for them.
Use case
An illustrative scenario, not a real incident.
A retried charge would bill twice. An idempotency key makes the repeat safe.
See it in different ways
sequenceDiagram participant M as Model participant A as Application participant T as Tool M->>A: Tool name and arguments A->>A: Validate arguments A->>T: Call T-->>A: Result or error A-->>M: Result as context
sequenceDiagram participant M as Model participant A as Application participant T as Tool M->>A: Tool name and arguments A->>A: Validate against the schema A->>T: Run, with an idempotency key T-->>A: Short result or clear error A-->>M: Result as context
flowchart TD
Q{"Has this key been seen?"}
Q -->|"Yes"| A0["Return first result"]
Q -->|"No"| A1["Charge once"]Key point: Idempotent calls make retries safe.
Why the other options are wrong
- A. Longer system prompts
- Length is unrelated.
- B. Larger output tokens
- Output size is unrelated.
- C. Top-p sampling
- Sampling is unrelated.