docs: add new post

[necatiozmen]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://voltagent.dev/docs/community/contributing/#commit-convention

Bugs / Features

• Related issue(s) linked
• Tests for the changes have been added
• Docs have been added / updated
• Changesets have been added https://voltagent.dev/docs/community/contributing/#creating-a-changeset

What is the current behavior?

What is the new behavior?

fixes (issue)

Notes for reviewers

---

Summary by cubic

Adds a new blog post introducing Tool Routing in VoltAgent—scaling tool use with a small router surface backed by a hidden tool pool via embeddings—with quick-start examples (pool vs expose, multiple routers, resolver mode) and notes on observability/guardrails. Also updates the docs navbar label to "VoltAgent Framework".

^{Written for commit 0c821fe. Summary will update on new commits.}

Summary by CodeRabbit

Documentation

• Added comprehensive guide on Tool Routing with details on embedding-based tool search, two-layer design patterns, customizable routing strategies, resolver modes, error handling, observability, and implementation best practices with code examples.
• Updated VoltAgent label to "VoltAgent Framework" in documentation navigation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0c821fe

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

📝 Walkthrough

Walkthrough

Additions include a new blog article introducing VoltAgent's Tool Routing architecture—a two-layer routing approach to reduce prompt bloat while maintaining control—and a UI label update clarifying the product name as "VoltAgent Framework" in the documentation navbar.

Changes

Cohort / File(s)	Summary
Blog Content website/blog/2026-01-23-tool-routing/index.md	New article explaining VoltAgent's Tool Routing concept, including embedding-based tool search, two-layer design patterns, resolver modes, and usage guidance
Navigation UI website/src/components/doc-navbar/index.tsx	Updated tab label from "VoltAgent" to "VoltAgent Framework" for product name clarification

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A blog hops into view so bright,
Tool Routing explained just right,
Framework named with clearer sight,
Documentation shines with light! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title is vague and generic. It says 'docs: add new post' but doesn't specify what the post is about, making it unclear from the title alone that this adds Tool Routing documentation.	Revise title to be more specific, e.g., 'docs: add Tool Routing blog post' to clearly indicate the main content being added.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description includes the template structure and an auto-generated summary that clearly explains the changes, but several required checklist items remain unchecked (commit message, related issues, tests, changesets).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cloudflare-workers-and-pages]

Deploying voltagent with    Cloudflare Pages

Latest commit:	0c821fe
Status:	✅  Deploy successful!
Preview URL:	https://ecc621c2.voltagent.pages.dev
Branch Preview URL:	https://add-tool-routing-post.voltagent.pages.dev

View logs

[cubic-dev-ai]

No issues found across 1 file

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

website/src/components/doc-navbar/index.tsx (1)

173-182: Align mobile label with updated tab name.
Desktop tab shows “VoltAgent Framework” while the mobile menu still shows “VoltAgent”.

🧩 Suggested fix

-              VoltAgent
+              VoltAgent Framework

🧹 Nitpick comments (1)

website/blog/2026-01-23-tool-routing/index.md (1)

33-33: Rephrase to avoid “issue you shared” in a public post.
This reads like a private conversation. Consider a neutral, public-facing phrasing.

💡 Suggested edit

-The VoltAgent issue you shared describes exactly this: frameworks tend to expose the full tool set directly, and prompt size becomes the scaling bottleneck.
+A common issue in agent frameworks is exposing the full tool set directly, making prompt size the scaling bottleneck.