Server has critical structural issues: 4 duplicate tool definitions (get_alerts, get_forecast, create_freshdesk_ticket appear twice), indicating poor tool registration. Descriptions are present but minimal (10-50 chars, below the 50-200 char baseline for LLM optimization). Parameters lack descriptions entirely in most tools, e.g., 'symbol' in calculate_moving_averages has a description, but 'short_period' and 'long_period' lack guidance on valid ranges. No output schemas documented. No error handling guidance. Tools mix weather, finance, and ticketing domains without clear composition. Duplicate tools suggest incomplete implementation or copy-paste errors.

• Remove duplicate tool registrations (tools 8-10 are exact copies of 5-7). Keep one canonical definition per tool.
• Add parameter descriptions to all inputs. For numeric params, specify min/max (e.g., 'short_period: 1-100 minutes, default 20'). For enums, list valid values (e.g., 'state: Two-letter US state code, e.g., CA, NY, TX').
• Document output schemas for each tool. Example: 'Returns {symbol: string, short_ma: float, long_ma: float, signal: string}'. Include pagination info if results can be large.
• Expand tool descriptions to 50-200 chars. Include WHEN to use: 'Calculate moving averages to identify trend reversals. Call after get_symbol_data() to analyze price momentum.'
• Add error handling guidance. Example: 'If symbol not found, try search_symbols(). If API timeout, retry after 5 seconds.' Use pattern:recovery-guide.