This is a template/scaffold server with only one example tool. The tool definition itself is present with schema and basic description, but the implementation quality reveals significant gaps. The tool name 'example_tool' is generic and lacks a clear action verb. The description is minimal (55 chars, below the 194-char baseline). The schema is present but parameter descriptions are perfunctory ('Example parameter description', 'Optional parameter description'). The server lacks proper error handling guidance, McpError conversions exist but don't inform the LLM what to do next. As a template, this is meant to be customized, but in its current form it does not meet production quality standards even as an example.

• Rename 'example_tool' to a concrete verb_noun pattern, e.g., 'fetch_resource', 'get_weather', 'search_database'. The new name should immediately convey the action.
• Expand tool description to 100 - 250 characters. Include: (1) what the tool does, (2) when to use it vs. related tools, (3) required setup or context. E.g., 'Fetch resource data from the {SERVICE} API. Use when you need to retrieve a single item by ID. Requires API key set in {SERVICE}_API_KEY.'
• Replace placeholder parameter descriptions with concrete constraints. E.g., 'exampleParam: A unique resource identifier (alphanumeric, 5 - 50 chars). E.g., "abc123" or "resource-dev-001". Required.' and 'optionalParam: Resource filter or option. Valid values: "summary", "detailed", "raw". Defaults to "summary" if omitted.'
• Document the return schema explicitly in the tool description or add it to the capabilities metadata. Specify: 'Returns an object with fields: id (string), name (string), status (string), created_at (ISO 8601 date), metadata (object). Example: {"id":"abc123", "name":"My Resource", "status":"active", "created_at":"2024-01-15T10:30:00Z", "metadata":{...}}'
• Enhance error messages to guide LLM recovery. E.g., for 404, return 'Resource not found. Verify the resource ID is correct. Call search_resources() with a partial name to find matching resources.' For 401, return 'Authentication failed. Check that your API key (from {SERVICE}_API_KEY env var) is valid and not expired.'
• Add per-parameter validation and error messages. When exampleParam is invalid, return 'Invalid exampleParam value. Must be alphanumeric, 5 - 50 chars. Received: "{received}". Valid example: "abc123".'