How would you decide whether a tool result should go back to the model or directly to the user?
Instruction: Describe how you decide where tool output should flow next.
Updated
Example Answer
I'd ask whether another model pass adds useful interpretation. A confirmed ticket update can be displayed directly with the stored status and operation reference. A search returning several relevant documents may need synthesis and citations.
Direct display still needs authorization, safe rendering, and appropriate redaction; raw tool output is not automatically user-ready. If I return data to the model, I'd bound it and treat embedded instructions as untrusted content. I'd keep deterministic facts, such as whether a write completed, anchored to the tool result rather than let the model embellish them. I'd compare latency and user understanding for both paths, including errors and partial outcomes, before choosing a default.
Why this works
Explains routing as a product decision while covering both rendering and model-context risks.
Practice follow-up
What should be shown directly when a write is only partially successful?
Your preparation path
Work through these questions in order. Read the answer aloud, then explain it in your own words.
1. Start with the foundations
Build the vocabulary and explain the core decisions.
2. Apply it to a real workflow
Practice diagnosis, validation, and everyday tradeoffs.
3. Prepare for senior discussions
Explain failure boundaries, recovery, and production choices.
- Design a fallback strategy when tools are unavailable, degraded, or unauthorized. Member answer
- How do you implement MCP step-up authorization without losing scopes or retrying forever? Member answer
- An MCP request resumes after user confirmation. How would you validate its requestState? Member answer
Related Questions
-
easy
-
easy
-
easy
-
easy
-
easy
-
easy