Single tool 'search_route' with comprehensive parameter schema and detailed descriptions. Schema is well-structured with proper Zod types and enums. However, output schema is not documented, the tool returns raw HTML-extracted text without specifying expected fields or structure. Description is very long (900+ chars) and includes extensive conversion tables that should be in a prompt or documentation, not the tool description itself. Tool name is clear (verb_noun pattern). Error handling is minimal, only catches and logs raw errors without recovery guidance.

• Document output schema: specify the expected structure of returned route data (e.g., routes array with departure/arrival times, stations, fares, transfer counts).
• Shorten tool description to 150-200 chars. Move conversion tables to the 'norikae-usage' prompt where they belong.
• Add error categorization: distinguish network timeouts (retryable) from invalid station names (user-fixable) and provide specific guidance for each.
• Implement result limits and indicate them in the description: 'Returns up to 5 route alternatives. Call again with different options to see more.'
• Consider parsing extracted HTML into structured JSON (routes with typed fields) instead of raw text, enabling safer LLM downstream processing.
• Add parameter validation with clear error messages: 'Station name must be in Japanese kanji/kana. Did you mean: 新宿 (Shinjuku)?'