Container Tool Contracts
Container-backed tools run heavier jobs outside the lightweight request path while keeping outputs connected to workspace artifacts.
Design Standard
- Use container tools for rendering, dataset processing, recordings, forecasts, and optimization.
- Track callbacks and outputs through operation history.
- Keep source artifacts linked to generated artifacts.
Review Questions
- What workspace context does the tool need?
- What does it return to the user or bot?
- Does it create or update artifacts, blobs, links, events, messages, or operations?
- How will a human review success or failure?
Media To Add
- Diagram: container request, callback, output blob, and operation update. It helps users understand asynchronous work. Source: document renderer or dataset renderer operation.