The server has 12 tools with mixed definition quality. Most tools have descriptions and basic schemas, but several lack proper parameter descriptions, input validation guidance, and error recovery context. Tool names follow verb conventions (add, create, get, search), which is positive. However, many parameters are underdescribed, output schemas are not explicitly documented, and error messages are generic. The definitions are serviceable but fall short of production-grade quality. Average tool score: 51.

• Document output schema for each tool. For example, add: { type: 'text', text: string } or { type: 'number', value: number }. For getWeather, document: { temperature, humidity, windSpeed, condition, sunrise, sunset }. For searchGitHubRepos, document: { name, owner, url, stars, language }.
• Enhance error messages with recovery guidance. Instead of '❌ 天氣查詢失敗: invalid city', return: 'City not found. Try searching with a country code (e.g., "Tokyo, JP") or check spelling. Available regions: Tokyo, Osaka, Kyoto.'
• Add format constraints to parameter descriptions. For convertUnits: 'fromUnit must be a valid unit symbol (e.g., m, km, ft, mi, kg, lb, °C, °F, L, ml).' For getCryptoPrice: 'symbol must be lowercase CoinGecko ID (e.g., bitcoin, ethereum, cardano).'
• Add range constraints to numeric parameters. For getTopTools: 'limit (1-100, default 10), days (1-365, default 30).' For getNews: 'Already present for limit, but add guidance for topic length (min 1 char, max 100).'
• Replace or remove getNews if real API integration is not feasible. Mock data undermines trust in the entire server. If you must mock, rename to 'getNewsMock' and document that it returns example data for testing only.
• Add idempotency hints to tools that create resources. For createFile, addTodo, createGitHubIssue: document whether duplicate calls with identical params create duplicates or return existing resources. If not idempotent, provide a way to check existence first.
• Document tool chaining requirements. For searchGitHubRepos output, include owner and repo names so createGitHubIssue can reference them directly without a separate lookup.