20 tools across two domains (expense tracking, math). All tools have descriptions and input schemas with typed parameters. However, descriptions are minimal (10-50 chars, well below the 194-char baseline), lack context on WHEN to use tools, and omit error guidance. No output schemas documented. Parameter descriptions are present but terse. No tool annotations (readOnlyHint/destructiveHint). Error handling is absent, no recovery guidance for invalid inputs. Composition is reasonable (single responsibility per tool), but descriptions do not explain dependencies or prerequisites. Average per-tool score: 52.

• Expand all tool descriptions to 50-200 characters. Include WHAT the tool does, WHEN to use it, and what it returns. E.g., 'list_expenses: Returns all recorded expenses as a list of {amount, category, description, date}. Call this to review spending history or before filtering by category.'
• Document output schemas for every tool. Specify field names, types, and whether results are paginated. E.g., 'Returns: {total: float, expenses: [{id: string, amount: float, category: string, description: string, date: ISO8601}]}'
• Add error handling guidance to descriptions. E.g., 'delete_expense: If index is out of range, returns error 'Index out of bounds. Call list_expenses to see valid indices.' If no expenses exist, returns 'No expenses to delete.'
• Add tool annotations: mark list_expenses, total_expenses, category_summary, and all math tools as readOnly=true. Mark delete_expense as destructive=true. Mark add_expense as idempotent=false (or omit if not idempotent).
• For delete_expense, implement a confirmation pattern: add a 'confirm' boolean parameter (default false) or a separate 'confirm_delete_expense' tool that requires explicit user approval before deletion.