Four tools with basic verb-noun naming (get_, list_, search_, update_). All have descriptions (10-60 chars, below baseline 194 avg). Input schemas present with type definitions but parameter descriptions are minimal or absent. No output schemas documented. No error handling guidance. Oversight/audit/masking applied but not explained in tool descriptions. Missing critical context for LLM selection and recovery.

• Expand tool descriptions to 100-200 chars. Example: 'get_employee: Retrieve employee record by ID. Returns name, email, and salary (redacted for viewer role). Throws 404 if ID not found, try search_employees() with partial name.'
• Document output schemas for all tools. Example: 'Returns {id: int, name: str, email: str, salary: int (redacted for viewer), role: str}'.
• Add parameter descriptions. For 'emp_id': 'Employee ID (integer, 1-999999). Returns 404 if not found.' For 'q': 'Search query string (1-100 chars). Matches name, email, or ID prefix.'
• Add error recovery guidance. Example: 'If employee not found, call search_employees() with a partial name to discover the correct ID.'
• Document permission rules in descriptions. Example: 'update_employee: Update salary. Requires admin role, viewer role is denied. Returns 403 Forbidden if insufficient permissions.'