Designing Simple Tool Interfaces › When Not to Use a Tool

Michael BrenndoerferJune 25, 20252 min read
AI Agent HandbookAll chapters
Part 5 of 15Tool Use - Extending the Agent's Abilities
Chapter 13Designing Simple Tool Interfaces › When Not to Use a Tool
Reading section 9 of 12 · When Not to Use a Tool · 2 minSection 9 of 12 · 2 min

Section 9 of 12 · 2 min read

Designing Simple Tool Interfaces › When Not to Use a ToolSection view · Sections in this chapter9 / 12 ↓
Reading tools Notes & comments
Notes & comments

An important part of tool design is knowing when the agent shouldn't use a tool. Not every question requires external information:

Code
CollapseExpand
User: What's the capital of France?

The agent can answer this from its general knowledge. It doesn't need to search the web or call an API. Using a tool here would be slower and waste resources.

Good tool use involves:

  • Using tools when needed: For current information, precise calculations, or actions
  • Not using tools when not needed: For general knowledge questions the agent can answer directly
  • Failing gracefully: If a tool isn't available or returns an error, the agent should explain the limitation

You can guide this behavior through your system prompt:

PythonIn [10]
CollapseExpand
system_prompt = """
You are a helpful assistant with access to tools.

Use tools when you need:
- Current, real-time information (weather, news, stock prices)
- Precise calculations
- To take actions (send emails, update records)

Do NOT use tools for:
- General knowledge questions you can answer directly
- Simple arithmetic you can handle reliably
- Questions about your own capabilities

If you're unsure whether to use a tool, prefer using it to ensure accuracy.
"""

Comments

Add to the conversation

A question, a correction, or an example from your own work.

No comments yet. Be the first to share your thoughts!

Newsletter

Stay up to date

Get new articles, book updates, and notes on AI and technology.

Unsubscribe at any time. Privacy policy