Understanding Tools

Learning Objectives

By the end of this lesson, you will be able to:

• Explain the purpose of tools in Agent OS

• Describe how tools expand an agent's capabilities

• Distinguish between triggers, tools, and instructions

• Understand how agents use tools to access and update information

• Identify common categories of tools available in Agent OS

What Are Tools?

If triggers tell an agent when to begin working, tools determine what the agent can do once it starts.

Tools provide access to systems, services, and actions outside of the agent itself.

Without tools, an agent can reason about information, but its ability to interact with the world is limited.

Think of tools as the agent's hands.

The agent can analyze information and make decisions, but tools allow it to retrieve data, update records, communicate with other systems, and complete tasks.

For example, an agent might:

• Read a content entry

• Update metadata

• Send a Slack message

• Retrieve information from another system

Each of these capabilities is provided through a tool.

Triggers, Tools, and Instructions

As you build agents, it's important to understand the relationship between triggers, tools, and instructions.

A trigger determines when the agent starts.

Instructions define what outcome the agent should achieve.

Tools provide access to the systems and actions required to achieve that outcome.

For example:

TriggerA new article is created.

InstructionsGenerate a teaser, SEO metadata, and tags.

ToolsRetrieve the article, update the entry, and notify the content team.

Each component plays a different role.

The trigger starts the work.

The instructions describe the goal.

The tools provide the capabilities needed to accomplish that goal.

Tools Do Not Replace Reasoning

One of the most common misconceptions about agents is that tools are what make them intelligent.

They are not.

The intelligence comes from the model's ability to analyze information, interpret context, and make decisions.

Tools simply provide access to information and actions.

Consider the difference between these two scenarios:

Traditional Automation

When a new article is created:

• Copy value from Field A

• Move value to Field B

• Send notification

The workflow follows a predefined set of rules.

No interpretation occurs.

Agent Workflow

When a new article is created:

• Retrieve the article

• Analyze the content

• Generate a teaser

• Create SEO metadata

• Suggest tags

The agent must understand the content before it can determine the appropriate output.

The tools enable access to the article and allow the results to be saved, but the reasoning happens between those steps.

The Tools We'll Use

Throughout this course, we'll use several Contentstack and Slack tools.

Get a Single Entry

This tool allows the agent to retrieve the content entry that triggered the workflow.

The agent can access information such as:

• Title

• Headline

• Article Body

• Existing metadata

Without this tool, the agent would know that an article was created but would not have access to the content itself.

Update Entry

This tool allows the agent to write information back to Contentstack.

We'll use it to populate fields such as:

• Teaser

• SEO Title

• SEO Description

• Tags

The agent generates the content and then uses the tool to save the results.

Slack

This tool allows the agent to communicate with users and teams.

Throughout the course, we'll use Slack to:

• Verify agent output

• Review generated content

• Confirm workflow execution

In real-world implementations, Slack is often used to notify stakeholders when agent-driven tasks are complete.

Choosing the Right Tools

A useful question to ask when building an agent is:

What information does the agent need, and what actions must it perform?

The answer helps determine which tools should be added.

For example:

If an agent needs to read content:

• Add a tool that retrieves content.

If an agent needs to update content:

• Add a tool that writes data back to the system.

If an agent needs to notify users:

• Add a communication tool.

Good tool selection starts with the business objective rather than the technology itself.

Focus on what the agent needs to accomplish, then choose the tools that support that outcome.

Key Takeaways

• Tools provide access to systems, services, and actions outside the agent.

• Triggers determine when work begins.

• Instructions define the desired outcome.

• Tools provide the capabilities required to achieve that outcome.

• Tools enable access to information, but reasoning is performed by the agent.

• The right tools are determined by the business problem you're trying to solve.

Next Lesson

Next, we'll combine triggers and tools to build the first working version of our Content Enrichment Agent and verify that it can retrieve, understand, and summarize content automatically.