<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tool Use on AIBussin — AI applications, systems and books</title><link>https://aibussin.com/tags/tool-use/</link><description>Recent content in Tool Use on AIBussin — AI applications, systems and books</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 08 Aug 2026 17:09:00 +0100</lastBuildDate><atom:link href="https://aibussin.com/tags/tool-use/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is an Agent, Really?</title><link>https://aibussin.com/books/agents-from-first-principles/01-chapter/</link><pubDate>Sat, 08 Aug 2026 15:40:00 +0100</pubDate><guid>https://aibussin.com/books/agents-from-first-principles/01-chapter/</guid><description>&lt;p&gt;This book is about building systems &lt;strong&gt;around&lt;/strong&gt; models. Before we build planners, memory, tool routing, critics, search and verifiers, we need an answer to a question that turns out to be harder than it looks:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;&lt;strong&gt;What is an agent?&lt;/strong&gt;&lt;/p&gt;&#10;&lt;/blockquote&gt;&#10;&lt;p&gt;The word is currently applied to almost everything: a single LLM call, a chatbot, a fixed pipeline, a tool-using loop, and any five model calls with class names ending in &lt;code&gt;Agent&lt;/code&gt;. Those systems may all be useful. But when one word covers all of them, it stops telling us anything about the computation, and we lose the ability to say which mechanism is doing the work.&lt;/p&gt;</description></item><item><title>Capabilities and Routing</title><link>https://aibussin.com/books/agents-from-first-principles/07-chapter/</link><pubDate>Sat, 08 Aug 2026 17:09:00 +0100</pubDate><guid>https://aibussin.com/books/agents-from-first-principles/07-chapter/</guid><description>&lt;p&gt;Every mechanism built so far has taken the action set as given. The action boundary validates a proposal against a fixed list of permitted action types. Candidate generation samples several proposals from the same list. The runtime-state chapter watches what happens after execution and decides whether to continue. All of them assume that somebody, somewhere, already decided which capabilities the policy could choose from.&lt;/p&gt;&#10;&lt;p&gt;So far we have treated that decision as an input. This chapter makes it explicit, because the capability surface changes the decision problem the policy has to solve and therefore belongs inside the agent architecture itself.&lt;/p&gt;</description></item><item><title>Agents From First Principles 00: What Is an Agent, Really?</title><link>https://aibussin.com/post/agents-from-first-principles-00/</link><pubDate>Sat, 08 Aug 2026 15:40:00 +0100</pubDate><guid>https://aibussin.com/post/agents-from-first-principles-00/</guid><description>&lt;h1 id="what-is-an-agent-really"&gt;What Is an Agent, Really?&lt;/h1&gt;&#10;&lt;p&gt;This is the first post in &lt;strong&gt;Agents From First Principles&lt;/strong&gt;.&lt;/p&gt;&#10;&lt;p&gt;It follows two earlier series.&lt;/p&gt;&#10;&lt;p&gt;In &lt;strong&gt;PyTorch: Zero to Hero&lt;/strong&gt;, we worked upward from tensors, autograd and neural-network building blocks until we could build a small language model ourselves.&lt;/p&gt;&#10;&lt;p&gt;In &lt;strong&gt;Models From First Principles&lt;/strong&gt;, we moved one level higher. We looked at how learned components can be composed into scorers, value models, policy heads, recurrent models, hierarchical models and compact recursive systems.&lt;/p&gt;</description></item></channel></rss>