Server has 5 tools with basic verb-noun naming (list_, get_, apply_). All tools have descriptions (10-60 chars), but most are too brief to guide LLM selection effectively. Input schemas are present but minimal: 3 tools have empty input objects (no parameters), 2 have single string params. No output schemas documented. No error handling guidance, no parameter constraints (enums, ranges), no idempotency hints. One tool (list_my_interest) is domain-mismatched (personal interests in a leave management system). Schemas lack depth, no min/max, no format specs, no dependency documentation.

• Add output schemas to all tools. E.g., list_employees should return {employees: [{id: string, balance: number}], total: number}. Document in tool description.
• Expand descriptions to 100-200 chars. Example: 'List all employees and their remaining leave balances. Call this first to see who is available before applying leave. Returns employee ID and days remaining.'
• Add parameter constraints: leave_dates as array with minItems=1, maxItems=365, items format='date'; employee_id as string pattern='^E\d{3}$' (or actual format).
• Implement error recovery guidance. E.g., apply_leave error: 'Insufficient leave balance. You requested {requested} days but have only {available}. Try get_leave_balance first to check availability.'
• Remove list_my_interest or move to a separate 'PersonalManager' server. Consolidate leave tools into one cohesive domain.