#tool-use
Every post tagged "tool-use".
76 posts · showing 71–76
-
Prompt, Tool, or Code? Where Each Piece of Logic Belongs
A rule the agent keeps breaking usually isn't a prompting failure — it's deterministic logic filed under "advice." Two questions place any behavior in the right one of three homes.
-
The Read-Only Agent That Wasn't: Auditing What Your Tools Can Actually Reach
A tool named `check_service_health` woke someone at 3am. Read-only is a claim about effects at the far end of every call, and there's a short audit that either proves it or shows you what you actually deployed.
-
Why Your Agent Stops Too Early: The Missing Termination Signal
"Done" in most agent loops means the model stopped asking for tools — indistinguishable from stuck, confused, or bored. Making completion an explicit, validated claim takes about twenty lines.
-
Your Tool Description Is a Prompt: Rewriting Schemas the Model Can Actually Follow
A three-word tool description sent an inbox agent after the wrong thread. Tool specs live inside the prompt, and five specific rewrites to yours will fix more wrong calls than any system-prompt rule.
-
The Confused Deputy in Your Agent: When the Tool Trusts the Model Too Much
Your refund tool checks whether the agent is allowed to issue refunds. Nothing checks whether the customer asking for one is entitled to it — and that gap opens without any jailbreak at all.
-
Your Agent Isn't Thinking, It's Looping — Read One Turn of the Trace
There's no reasoning engine and no memory — just a while-loop, a stateless model, and an array that grows. Unroll one turn of it and most agent mysteries stop being mysteries.