When to reach for it
- Many tools are managed.
- Selection and versioning are critical.
- Tools are shared across multiple agents.
Tool Registry.
A catalog, not a kitchen sink.
Available tools are centrally registered alongside their schemas, descriptions, permissions, and metadata.
In practiceA research agent queries a tool registry to discover and invoke a real-time web-search tool it has never been hardcoded to call.
When it backfires
- Only a few static tools exist.
- The registry cannot be maintained.
- Tool descriptions cause poor automated selection.
The tradeoff
Better tool governance is achieved against higher maintenance effort.
What it actually does.
The agent looks a tool up in a registry before calling it.
Two ways this pattern will hurt you.
Tool sprawl without deprecation
The registry grows to 200 tools, many of which are broken or superseded. The agent wastes turns calling stale tools.
Fix · Add a deprecation flag and a last-used timestamp. Prune tools unused for 90 days after audit review.
Missing capability metadata
The registry stores names and schemas but omits latency, cost, and reliability metadata. The agent can't make informed choices.
Fix · Require every registered tool to include a capability card: latency SLA, cost per call, and reliability score.
Where Tool Registry is native.
Microsoft Agent Frameworktool catalogNative
Next pattern