ExpenseTracker has three tools with visible schemas and descriptions, but quality is significantly below production baseline. Tool descriptions are written in Hindi-English mix (e.g., 'Claude is tool ko use karke...') which is unprofessional and unclear for LLM parsing. Descriptions lack actionable detail about when to use each tool vs. alternatives. Parameter descriptions are minimal (e.g., 'Date of the expense' with no format guidance). No output schemas documented. No error handling guidance. No input validation hints. Tool names are acceptable (add_expense, list_expenses, summarize) but descriptions fail to explain dependencies or expected formats. The 'summarize' tool's category parameter defaults to null but lacks clarity on behavior when omitted.

• Rewrite all tool descriptions in clear, professional English. Example: 'add_expense: Records a new expense transaction. Use when the user reports spending money. Returns the expense ID for reference in future queries. Requires date in YYYY-MM-DD format, amount as a number, and category from the available categories resource.'
• Document output schemas for each tool. Example for add_expense: 'Returns {"status": "ok"|"error", "id": integer, "message": string}'. For list_expenses: 'Returns array of {"id": integer, "date": string (ISO 8601), "amount": number, "category": string, "subcategory": string, "note": string}'.
• Add format constraints to date parameters: 'Date in YYYY-MM-DD format (e.g., 2026-06-15). Must be a valid calendar date.' Include min/max for amount: 'Amount in currency units, must be > 0 and <= 999999.'
• Add pagination to list_expenses and summarize: introduce 'limit' (default 20, max 100) and 'offset' (default 0) parameters. Return total_count in response so LLM knows if more results exist.
• Add error handling: validate date format before querying; return 'Invalid date format. Use YYYY-MM-DD (e.g., 2026-06-15).' If no results, return 'No expenses found for this date range. Try expanding the range or check available categories.' Include category enum or reference the categories resource.