From eede9059b64a05b6a6f5eb3f21e365ccf27bdb50 Mon Sep 17 00:00:00 2001
From: Karunanidhi Mishra <11963379+kmishra1204@users.noreply.github.com>
Date: Sat, 4 Jul 2026 17:37:51 -0500
Subject: [PATCH] Docs: clarify community tool sharing

---
 .../en/guides/tools/publish-custom-tools.mdx   | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/docs/edge/en/guides/tools/publish-custom-tools.mdx b/docs/edge/en/guides/tools/publish-custom-tools.mdx
index 71dbfd6221..0c1d466c35 100644
--- a/docs/edge/en/guides/tools/publish-custom-tools.mdx
+++ b/docs/edge/en/guides/tools/publish-custom-tools.mdx
@@ -303,3 +303,21 @@ agent = Agent(
     # ...
 )
 ```
+
+### Sharing Community Tools
+
+Keep the package README as the primary source of truth for installation, setup, security notes, and usage examples.
+This lets users evaluate the package from PyPI or its source repository without needing a CrewAI docs release.
+
+If you want to propose a CrewAI docs mention for a community-maintained tool, open a docs issue or PR with:
+
+- Package name and PyPI link.
+- Source repository link and license.
+- Supported CrewAI versions.
+- Installation command.
+- Minimal usage snippet that imports the package and attaches the tool to an agent.
+- Required environment variables or external services.
+- Maintenance status, known limitations, and any data handling or security considerations.
+
+Prefer a concise pointer to the external package over duplicating full package documentation in the CrewAI docs.
+If the tool should ship as part of the official `crewai_tools` package instead, follow the repository's normal contribution process.