mcp-go provides a framework for building MCP servers with basic tool support. However, tool definitions are severely underdeveloped. Of 7 tools, 2 lack descriptions entirely (notify, test-tool). Most descriptions are minimal (10-30 chars), well below the 50-200 char LLM-optimized baseline. Parameter descriptions are sparse or missing. Tool names lack action verbs (getTinyImage, longRunningOperation). No output schemas documented. Error handling is absent. The framework itself is sound (proper JSON Schema support, functional options pattern), but example tools demonstrate poor definition practices that would not pass production code review.

• Add descriptions to all tools. Minimum 50 chars; target 100-150. Example: 'Echoes back a message string. Use to test connectivity or verify input handling. Returns the exact input message.'
• Rename tools with action verbs: getTinyImage → get_image, longRunningOperation → run_async_task, notify → send_notification. Follow verb_noun convention.
• Document output schemas for every tool. Example for echo: {"type": "object", "properties": {"message": {"type": "string", "description": "The echoed message"}}}
• Add parameter descriptions with units and constraints. Example: 'duration: Duration in seconds (1-3600). Defaults to 10 seconds.' instead of 'Duration of the operation in seconds'.
• Add error handling guidance. Example: 'If duration exceeds 3600, returns error: "Duration must be ≤3600 seconds. Try a shorter duration."'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry