Server has 4 tools with complete schemas and descriptions, but quality is uneven. get_blended_stats has a complex, well-structured schema with proper enums and nested objects. All tools have descriptions (10-50 chars), but most are generic and lack actionable context. Parameters are typed but lack depth, no guidance on valid ranges, formats, or dependencies. Error handling returns raw API messages without recovery guidance. No tool annotations (readOnlyHint, idempotentHint). Output schemas are not documented. Descriptions average 35 chars (below 194-char baseline for A+ tools). No parameter descriptions beyond names.

• Expand descriptions to 100-200 chars. For get_shop_info: 'Retrieve shop metadata including name, ID, currency, and timezone. Call this first to verify shop configuration and get the shop_id for other queries.' This guides when to use it.
• Document output schemas for all tools. E.g., 'Returns {shop_id: string, name: string, currency: string, timezone: string}'. LLMs need to know what fields to expect.
• Add parameter descriptions to empty-schema tools. Even though they take no input, add a note: 'This tool requires no parameters. Ensure TRIPLE_WHALE_API_KEY and TRIPLE_WHALE_SHOP_ID are set in environment.'
• Improve error messages with actionable recovery. Instead of 'Error fetching blended stats: {error}', return 'Invalid date range: start must be before end and in YYYY-MM-DD format. Example: start=2024-01-01, end=2024-01-31.'
• Add tool annotations. Mark all tools with readOnlyHint=true (they are read-only). This helps agents understand they are safe to retry and do not modify state.