On its own, a model can only produce text. It can't check the weather, open a file or read your inbox. Tools change that.
What a tool is
A tool is something the bot can call to do a step. The model decides it needs to search, so it asks the search tool. The tool runs and hands back the result. Then the model keeps going.
xAI's docs call this function calling. They list built-in tools for Grok models like web search, X search and code execution, and you can define your own functions (docs.x.ai).
What a connector is
A connector is a tool hooked to one of your accounts: email, calendar, file storage, chat. Once connected, the bot can work inside that account using the access you granted.
That's powerful. It's also where things can go wrong.
| Tool type | Example | Risk |
|---|---|---|
| Read-only lookup | Web search | Low: it can read, not change |
| Read your accounts | Search your inbox | Medium: it can see private data |
| Write to your accounts | Send email, edit a calendar, delete a file | High: it can act in your name |
Every tool is a door
When you hire someone, you don't hand over every key on day one. You give them the keys for their job. A shipping clerk gets the dock door, not the safe.
Bots are similar. Give a bot the tools its job needs and no more. A bot that drafts replies needs to read email. It may not need to send it.
Reading isn't acting
The big line is between reading and acting. Reading your calendar to find a free slot is low-stakes. Sending an invite to a customer in your name is not.
Good bot setups draw that line clearly: the bot can read and draft freely, but anything that sends, posts, spends or deletes waits for a person's yes. See Nothing ships without a yes.
Tools are also suppliers
Every connector is an outside service your bot depends on. If it changes or goes down, your bot's work changes too. ISO calls this controlling external providers. See Suppliers: connectors, models and other people's bots.
A real example
Our own bots read the owner's email and calendar to prepare drafts. When a message should go out, the bot drafts it and the owner approves it. The bot has the hands to do the work, but the send button stays with the owner.
What this means for you
- List each bot's tools. You should be able to say what doors each bot has.
- Start read-only. Add write access when the bot has earned it.
- Gate the actions. Sending, spending, posting and deleting need a yes.
- Remove what's unused. An open door nobody uses is still open.
Tools are what turn a smart chat into a worker. Hand them out the way you'd hand out keys.