Two tools with complete schemas and descriptions, but descriptions are overly long (Japanese text, 200+ chars) and lack LLM-optimized structure. Parameter descriptions are present but minimal. No output schema documentation. Error handling exists for check_vacancy but lacks recovery guidance. lookup_store lacks error handling entirely. Tool names are action-oriented (lookup_, check_) but descriptions read like API docs rather than agent guidance.

• Rewrite tool descriptions to 50-150 chars, English, action-focused: 'lookup_store: Find Kaikatsu Club locations by name, prefecture, city, or code using AND search. Returns store details and available services.' check_vacancy: 'Check real-time seat availability at a Kaikatsu Club location by store code.'
• Document output schemas in tool descriptions or as structured comments. E.g., 'Returns: {total: number, truncated: boolean, results: [{store_code, store_name, prefecture, services[], playables{karaoke?, darts?, billiards?}}]}'
• Add error recovery hints to descriptions: lookup_store should note 'Returns empty array if no matches found'; check_vacancy should note 'Returns error if store_code invalid, use lookup_store to find valid codes.'
• Enhance parameter descriptions: 'keywords: Array of search terms (store name, prefecture, city, address, or store code). All terms must match (AND logic). E.g., ["北海道", "旭川"] finds Asahikawa stores in Hokkaido.' store_code: 'Numeric store identifier returned by lookup_store. E.g., "20176".'
• Add optional limit and offset parameters to lookup_store to enable pagination: 'limit (1-100, default 10): Max results per call. offset (default 0): Skip first N results. Allows fetching beyond initial 10-result cap.'