Two tools with basic descriptions and visible schemas, but significant gaps in parameter documentation and output structure. search_employees has 8 optional parameters with minimal descriptions (e.g., 'Filter by skill name' is generic). query_graph has only 1 required parameter. Neither tool documents return structure or pagination. Error handling returns plain strings rather than structured responses. No parameter constraints (enums, ranges) despite many accepting free-form strings. Descriptions are adequate (100-150 chars) but lack actionable guidance on when to use each tool or how they differ.

• Add enum constraints to parameters: department should list valid departments; certification should list known certifications. Replace free-form strings with validated options.
• Document output schema explicitly: 'Returns array of employee objects with fields: name (string), title (string), location (string), companies (array), skills (array of {name, level}), certifications (array).'
• Add parameter interdependency notes: 'skill_gap_with requires name parameter. If name is omitted, skill_gap_with is ignored.' Document which parameter combinations are valid.
• Implement structured error responses: return JSON with {error: string, code: string, retryable: boolean, suggestion: string} instead of plain text. Guide LLM recovery.
• Add pagination to search_employees: accept limit (1-100, default 20) and offset parameters; return {results: [...], total: N, has_more: boolean}.