Server has 4 tools with complete input schemas and basic descriptions. All tools are READ_ONLY and properly use Zod for schema validation. However, descriptions are minimal (10-30 chars), lacking context on WHEN to use each tool or dependencies between them. Parameter descriptions are present but terse. No output schema documentation. Error handling returns generic error text without recovery guidance. Tool names follow verb_noun pattern correctly but descriptions do not meet the 50-200 char LLM-optimized baseline (194 char average for A+ tools). Missing tool annotations (readOnlyHint present implicitly via risk field, but not in schema).

• Expand tool descriptions to 50-200 characters. Example: 'get-user-profile' → 'Fetch a GitHub user's profile including name, bio, location, follower count, and repository statistics. Use this to learn about a developer or verify a user exists before calling other tools.'
• Document output schemas for each tool. Define the structure of returned objects (e.g., profileInfo has fields: login (string), name (string), bio (string), followers (number), etc.). This enables LLMs to plan downstream operations.
• Enhance error messages with recovery guidance. Instead of 'Error fetching GitHub profile: 404', return 'User not found. Verify the username is correct (GitHub usernames are case-insensitive alphanumeric). Try search_repositories_by_topic to find related projects if the user is unknown.'
• Add parameter constraints and format hints. E.g., 'username: GitHub username (alphanumeric, 1-39 chars, case-insensitive)' and 'token: GitHub personal access token with repo scope (optional; required for private repos and higher rate limits).'
• Add tool annotations to schema. Include readOnlyHint: true in tool definitions to signal to clients that these tools are safe to call without user confirmation and can be cached.