Server provides 9 calendar/lunar tools with basic schemas and descriptions in Chinese. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are minimal (10-80 chars, well below the 194-char baseline), lack actionable context for LLM selection, and omit output schema documentation. No error handling guidance, no parameter constraints (enums), no pagination for list-like tools (get_holidays, get_solar_terms). Tools return JSON strings rather than structured objects, forcing LLM parsing. No tool annotations (readOnlyHint present but not declared). Naming is clear (verb_noun pattern) but descriptions don't explain WHEN to use each tool or dependencies between them.

• Expand tool descriptions to 100-200 chars. Include WHEN to use (e.g., 'Use solar_to_lunar to convert a Gregorian date to lunar calendar. Call get_date_info if you need all calendar info at once.').
• Document output schemas explicitly. E.g., 'Returns DateInfo with fields: solar (str), lunar (LunarDate), zodiac (str), festivals (list[str])'.
• Add pagination to get_holidays, get_solar_terms, get_lucky_days. Accept limit (default 20, max 100) and offset parameters. Return total_count.
• Add input validation and error messages. E.g., 'Invalid date format. Expected YYYY-MM-DD. Got: {input}. Valid range: 1900-2100.'
• Declare readOnlyHint: true in all tool schemas to signal idempotency and enable LLM caching optimizations.