Tool Use
Tools let agents do work that plain text cannot: read artifacts, inspect blobs, render documents, query datasets, analyze media, create links, submit forms, forecast time series, or call external capabilities.
When Tools Are Used
A bot may call a tool when a task requires structured data, file-backed content, external analysis, or a durable workspace change. Tool availability depends on workspace settings, bot configuration, and the specific runtime context.
What To Review
For tool-backed work, review:
- which tool was called
- what input context was used
- what output was returned
- whether a new artifact, blob, link, event, or operation step was created
- whether the result has limits or failure messages
Tool Categories
- Native tools operate directly on workspace concepts such as artifacts, links, events, forms, memory, and channels.
- Container-backed tools handle heavier rendering, dataset, recording, forecasting, and optimization workflows.
- Dynamic Worker tools support workspace-defined compute capabilities.
- MCP-projected tools let compatible external servers appear inside the workspace tool surface.
Media To Add
- Screenshot: operation timeline showing a tool call expanded with inputs and outputs. It helps reviewers understand tool-backed decisions. Source: sample bot operation using a document or dataset tool.
- Table: tool category, example tools, typical outputs, and review habit. It helps admins decide which tools to enable. Source: tools section and sample operations.