Single tool 'search' has a basic but incomplete definition. The schema is present and properly typed (query required, code and language optional), but the description is extremely thin (11 words), below the 20-character threshold that triggers a hard cap. The tool lacks output schema documentation, does not declare what it returns, and provides no guidance on error conditions or when to use it vs alternatives. Parameter descriptions are minimal but present. No tool annotations, no pagination, no structured output guidance. The implementation shows hardcoded analysis text that doesn't match the Perplexity API call, suggesting incomplete or copy-pasted logic.

• Expand tool description to 50 - 150 characters explaining: (1) what the tool does (searches Perplexity AI for coding solutions), (2) when to use it (when user has a coding error or design question), (3) what it returns (detailed analysis with root cause, step-by-step fix, and code examples). Example: 'Search Perplexity AI for expert analysis of coding errors. Provide a code snippet and error message; returns root cause analysis, step-by-step solutions, and corrected code examples.'
• Document the output schema explicitly in comments or via a JSDoc block. Example: 'Returns: { type: 'text', text: string } with sections: 1. Root Cause Analysis, 2. Step-by-Step Solution, 3. Best Practices, 4. Code Examples (before/after/alternatives).'
• Add comprehensive parameter descriptions: (1) query: 'The coding error message, exception, or design question (required; 10 - 2000 chars)', (2) code: 'The code snippet to analyze (optional; will be formatted as markdown code block; max 5000 chars)', (3) language: 'Programming language for syntax highlighting (optional; defaults to "auto"; supported: python, javascript, typescript, java, c++, c#, go, rust, php, ruby, or "auto" for detection).'
• Implement proper error handling. Wrap axios call in try-catch. Return McpError with ErrorCode.InternalError for Perplexity API failures, with message like: 'Perplexity API error: [status] [message]. Retry in 30s. If credentials fail, check PERPLEXITY_API_KEY environment variable.'
• Remove or fix the hardcoded analyzeCode placeholder logic. Either (1) call the Perplexity API for all requests consistently, or (2) clearly document when local analysis vs API calls are used. Currently the code returns fabricated output that doesn't match the query.