Three tools present with minimal quality. Tool definitions are visible in cosmosdb-mcp-server.ts but lack rigor. 'Weather' is a placeholder unrelated to Cosmos DB domain. 'searchProducts' and 'getOrders' have descriptions (10-50 chars, below 194-char baseline) and input schemas with single string parameters. No output schemas documented. No error recovery guidance. No parameter constraints, enums, or validation hints. Descriptions do not explain WHEN to use each tool or what fields are returned. No tool annotations (readOnlyHint present in metadata but not in schema). Naming is acceptable (verb_noun pattern) but descriptions are too terse to guide LLM selection.

• Document output schemas for searchProducts (return fields: id, type, brand, name, description, price, embedding_distance) and getOrders (return fields: id, email, items, total, createdAt, status). Include field types and descriptions.
• Expand tool descriptions to 100-200 chars. Example: 'searchProducts: Search the product catalog using vector embeddings. Returns top 10 matching products with price and description. Use when user asks for product recommendations or searches by feature.'
• Add parameter descriptions explaining format and constraints. Example: 'query: Free-text search string (1-500 chars). Converted to embeddings for vector similarity search. E.g., "wireless headphones under $100"'.
• Implement structured error responses with recovery hints. Example: '{"error": "Cosmos DB query timeout", "retryable": true, "suggestion": "Try with a shorter query or narrower date range"}'.
• Remove or replace Weather tool with a domain-relevant tool (e.g., getProductRecommendations, listCategories) to improve server coherence.