The Unipile MCP server presents 8 tools with basic structure but significant quality gaps. Tool naming follows verb conventions (list_, get_, delete_, reconnect_, resync_, connect_, solve_), which is good. However, descriptions lack depth and actionable context. Parameters are present with types and descriptions, but many descriptions are too brief (under 50 chars) and lack format constraints, validation guidance, or dependency hints. Output schemas are not documented, the code shows API passthrough without schema shaping. Error handling is absent: no recovery guidance, no error categorization, and raw API errors would propagate to the LLM. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are visible in the code. The server declares 8 tools total but sources indicate 96 tools are claimed in comments; only 8 are shown in the provided code, suggesting incomplete implementation or documentation mismatch. Across the visible tools, average description length is ~95 chars (below the 194-char baseline for production tools), and parameter descriptions are minimal (30-60 chars vs. 72-char baseline).

• Add output schema documentation to every tool. Example: 'Returns {account_id: string, provider: string, status: enum[connected|disconnected], last_sync: ISO8601}' in tool docstrings or FastMCP tool metadata.
• Implement error handling middleware that catches exceptions, categorizes them (retryable/user-fixable/fatal), and returns structured error responses: {error: string, code: string, suggestion: string}.
• Add readOnlyHint=true annotation to list_accounts, get_my_profile, get_account. Add destructiveHint=true to delete_account. Use @mcp.tool(hints={...}) or similar FastMCP mechanism.
• Replace plaintext password parameter in connect_account with OAuth redirect URL or require pre-configured secure authentication. Never expose credentials in tool parameters.
• Expand descriptions to 80 - 150 chars with explicit context: 'Delete a connected account permanently (irreversible). Use when revoking access. Returns success or error details. Call list_accounts first to confirm the account exists.'
• Add pagination to list_accounts: include limit (default 50, max 200), offset, and total count in response. Cap default results to prevent context window exhaustion.
• Validate all parameters early and return actionable error messages. E.g., for account_id: 'Invalid account_id format. Expected UUID. Available accounts: account-123, account-456'.
• Document parameter format constraints explicitly. E.g., account_id: 'UUID format (8-4-4-4-12 hex chars)'; google_scopes: 'Comma-separated OAuth scope URLs, max 6, e.g. https://www.googleapis.com/auth/gmail.readonly'.

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

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