all answers

General agent concepts

Tool calling

Tool calling is how a language model acts outside its own text. The model is given a set of tool definitions, each with a name, a description, and an argument schema. When it decides a tool is needed, it emits a structured call naming the tool and its arguments, the runtime executes the call, and the result goes back into the model's context. The model can then answer or chain further calls, and an agent is essentially this loop run until the task is done. Three model-side steps sit inside it: choosing the tool, forming the arguments, and interpreting what comes back.

It exists because a model on its own can only generate text from what's already in its context. Tools let it fetch data that changes, like a database row, a search result, or a calendar, run computation it can't do reliably in its head, and take real actions like sending a message, editing a file, or calling an API.

An agent reaches for a tool when the task needs something outside the model's context or beyond text generation: current state it can't know, an action with side effects, or an answer that has to be exact where a plausible guess isn't enough. The tool definitions the agent carries set what it can do. Which tool the model picks, and the arguments it forms, decide what it actually does.

15 questions

Answered, plainly.

Why did my agent call the wrong tool with invented arguments?The model matched your request to the tool whose description sounded closest, then filled a gap in the arguments with a plausible guess instead of a real value.answer →Can parallel tool calls break if one depends on the other running first?Yes. Running two tools at once removes the ordering their logic depended on, and the dependent one can execute before its precondition exists.answer →Does tool selection accuracy get worse as an agent gets more tools?Yes. Narrowing a five-tool list down to only what a query needs raised selection accuracy on medium-difficulty queries by 16 percentage points in one study.answer →How reliable are MCP tool calls in production?Not very, on average: a 2026 stress test of 100 MCP servers found a median 71% pass rate per call, which compounds to about 18% across a five-call chain.answer →What's the difference between tool calling and function calling?There's no real difference: OpenAI and Google call it function calling, Anthropic calls it tool use, and tool calling is the vendor-neutral term for all of them.answer →What are the ways a single tool call can fail?A tool call fails in one of three places: the model picks the wrong tool, it fills in the wrong arguments, or it misreads what the tool returns.answer →What is tool calling?Tool calling is how a language model acts outside its own text: it emits a structured call naming a tool and its arguments, and a runtime executes it.answer →Why does renaming a tool's parameter break my agent even though my tests still pass?Because the model chooses tools and fills arguments by reading the parameter's name and description at inference time, and no code test checks that.answer →What's the difference between tool calling and MCP?Tool calling is the model choosing a function and filling its arguments; MCP is a protocol for where that function's definition and execution live.answer →What's the difference between tool calling and RAG?Tool calling is the model deciding, mid-response, to fetch something or act; RAG retrieves documents automatically before the model answers, no decision involved.answer →What's the difference between tool calling and structured output?Tool calling lets the model invoke a function mid-response and get a result back; structured output only constrains its final answer's JSON shape.answer →What's the difference between tool calling and code execution?Tool calling puts every call and result through the model's context one at a time; code execution has the model write code that calls several tools itself, in a sandbox.answer →What's the difference between tool calling and the ReAct pattern?Tool calling is the model emitting a structured call naming a function and its arguments; ReAct is an older prompting pattern that interleaves a reasoning step with each action.answer →What's the difference between tool calling and an agent?Tool calling is a single capability: picking a function and reading its result. An agent is the loop that calls tools repeatedly, deciding what's next itself.answer →What is an agent trajectory?The full record of one run: every state the agent saw, every action it took, and every observation that came back, in order, not just the final answer.answer →

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y