docs: clarify tool description field requirements and client compatibility

msanatan · msanatan · commit 1d5291e9e243 · 2025-10-03T18:27:10.000-04:00
diff --git a/docs/CUSTOM_TOOLS.md b/docs/CUSTOM_TOOLS.md
@@ -59,7 +59,9 @@ def my_custom_tool(
 )
 ```
 
-You can use all options available in FastMCP's `mcp.tool` function decorator: <https://gofastmcp.com/servers/tools#tools>. The `description` is the only required field.
+You can use all options available in FastMCP's `mcp.tool` function decorator: <https://gofastmcp.com/servers/tools#tools>.
+
+**Note:** All tools should have the `description` field. It's not strictly required, however, that parameter is the best place to define a description so that most MCP clients can read it. See [issue #289](https://github.com/CoplayDev/unity-mcp/issues/289).
 
 ### Auto-Discovery
 

Original file line number	Diff line number	Diff line change
`@@ -59,7 +59,9 @@ def my_custom_tool(`
`59`	`59`	`)`
`60`	`60`	```
`61`	`61`
`62`		-You can use all options available in FastMCP's `mcp.tool` function decorator: <https://gofastmcp.com/servers/tools#tools>. The `description` is the only required field.
	`62`	+You can use all options available in FastMCP's `mcp.tool` function decorator: <https://gofastmcp.com/servers/tools#tools>.
	`63`	`+`
	`64`	+Note: All tools should have the `description` field. It's not strictly required, however, that parameter is the best place to define a description so that most MCP clients can read it. See [issue #289](https://github.com/CoplayDev/unity-mcp/issues/289).
`63`	`65`
`64`	`66`	`### Auto-Discovery`
`65`	`67`