Single tool with critical definition gaps. Tool name 'github_user_lookup' lacks action verb prefix (should be 'get_github_user' or 'lookup_github_user'). Description is generic ('Verified API tool recipes for AI agents') and does not explain what the tool does, when to use it, or what it returns, fails the 10-1024 character guideline for meaningful content. Input parameter 'username' has description 'path' (3 chars), far below the 20-char minimum and provides zero context. No output schema documented in the tool registration despite returning structured ToolOutput. Tool annotations present but descriptions absent make them useless to LLMs.

• Rename tool to 'get_github_user' to follow verb_noun convention and clarify the action.
• Replace tool description with: 'Fetch public GitHub user profile data by username. Returns user ID, name, bio, followers, public repos, and other profile metadata. Use this to look up GitHub user information when you have their username.'
• Replace parameter description 'path' with: 'GitHub username (e.g. octocat). Case-insensitive. Required.'
• Register outputSchema in server.registerTool() so LLMs know the response contains {status: number, ok: boolean, body_preview: string}.
• Add error handling: catch fetch failures and return actionable messages like 'User not found. Check the username spelling and try again.' or 'GitHub API rate limit exceeded. Try again in a few minutes.'