Session brief
Tool Calling Is Not Just Plumbing for AI Agents — Roy Derks
Overview
This talk argues that tool calling is a critical, often overlooked component of AI agent development, deserving more attention than the agents themselves. The speaker emphasizes that an agent's effectiveness is directly tied to the quality, reusability, and robustness of its tools. The presentation explores different approaches to tool integration, from traditional, explicit tool calling to more embedded methods, and advocates for architectural patterns that promote separation of concerns.
Who should watch
- AI Engineers building agentic systems
- Product Managers evaluating agent capabilities
- Developers seeking to improve the reliability and flexibility of AI tools
- Anyone frustrated by brittle tool integrations in AI agents
Key takeaways
- The quality and reusability of tools are paramount to an agent's overall performance.
- Traditional tool calling involves explicit logic for identifying and executing tools, often leading to complex application code.
- Embedded tool calling, common in many frameworks, hides the tool execution logic within the agent, offering simplicity but reducing control.
- Architectural patterns like MCP (Model Context Protocol) and standalone tool platforms promote separation of concerns, allowing tools to be developed and managed independently of agent frameworks.
- Dynamic tools, generated from schemas (e.g., GraphQL, SQL), offer a flexible alternative to static tool definitions, reducing the need to create numerous specific tools.
- Separating tool development and execution from agent frameworks enhances flexibility, making it easier to switch between different agentic systems.
- While models are improving, the application layer, including tool integration, requires significant development effort to catch up.
Notable quotes
*The agent is only as good as their tools.*
*The application layer especially the bar where you build your tools deserves more attention.*
*As a developer I really like to separate concerns.*
Unofficial community note. Prefer the recording for nuance.