Single tool with acceptable description but weak schema definition and no output schema documentation. Tool is explicitly registered in src/index.ts with server.registerTool(). Description is substantive (236 chars, within baseline 194 avg), but input schema is minimalist with only one parameter (prompt:string) lacking structured output documentation. No parameter validation, enum constraints, or error handling guidance. Missing pagination, limits, and response field documentation. The tool delegates to an external Yachtsy API via OpenAI client, but the server does not document what structure clients should expect or how to handle errors beyond a generic try-catch.

• Define a complete output schema with typed fields: { yacht_listings: [{ id, name, price, location, specs }], market_analysis?: string, sailing_advice?: string, error?: null|string }. Document in tool description and JSDoc.
• Add input parameter constraints: prompt must be 5 - 1000 chars; optional parameters for query_type enum (listings|analysis|advice|general) and limit (1 - 100, default 20).
• Implement error classification: return { isError: true, errorType: 'API_UNAVAILABLE'|'INVALID_QUERY'|'RATE_LIMITED'|'UNKNOWN', suggestedAction: 'retry'|'reformulate'|'wait', message: 'Specific, actionable error text' }.
• Rename tool to 'query_yachtsy_marketplace' or 'search_yachts' to follow verb_noun naming convention and clarify the action.
• Add parameter descriptions: 'Your natural language query (5 - 1000 chars). Examples: "Catalina 34 sailboats under $100k", "Best bluewater cruising boats", "Yacht listings in Florida".' Remove example values from description and move to parameter schema pattern or enum.
• Implement result pagination: add optional limit (default 20, max 100) and offset or cursor parameters. Return total_count and next_cursor in response so LLM knows whether more results exist.
• Refactor secret handling: inject YACHTSY_API_KEY from environment during server initialization, not from user config. Use ServerInitOptions or a vault library to prevent credentials in logs.