Server has 6 tools with basic naming and descriptions, but significant gaps in schema completeness and parameter documentation. Tools 5-6 (get_toolset_tools, enable_toolset) have empty enum constraints in their 'toolset' parameter, making schemas incomplete. Descriptions are present but brief (avg ~100 chars, below the 194-char baseline). No documented output schemas visible. Error handling and recovery guidance absent. Tool composition is reasonable (single responsibility), but parameter descriptions lack detail on constraints, formats, and valid ranges.

• Populate enum constraints for 'toolset' parameter in get_toolset_tools and enable_toolset. Query available toolsets at server startup and inject them into the schema.
• Document output schemas for all tools. Specify what fields each tool returns (e.g., get_me returns {id, login, name, email, ...}; list_available_toolsets returns {toolsets: [{name, enabled, description}, ...]}). Include these in tool definitions or a separate schema document.
• Expand parameter descriptions to include format, length, and valid value guidance. E.g., 'user: GitHub username (alphanumeric, 1-39 chars) or email address. If not provided, uses authenticated user.'
• Add error recovery guidance to tool descriptions. E.g., 'If the team is not found, call list_available_toolsets to discover available teams, or verify the org and team_slug are correct.'
• Extend tool descriptions to explain workflow and dependencies. E.g., 'Call list_available_toolsets first to see available toolsets, then get_toolset_tools to inspect capabilities, then enable_toolset to activate.'