Single tool with clear naming (github_repo_stats) and adequate schema. Description is concise (97 chars, within 10-1024 range). Input schema properly defined with Zod, both parameters typed and described. However, output schema is not formally documented in the tool definition, only visible in the implementation. No error handling guidance, no parameter constraints (e.g., owner/repo format validation), and no mention of rate limits or prerequisites. Follows basic pattern:tool but lacks depth in error recovery and output documentation expected of production tools.

• Document output schema in tool definition: 'Returns object with fields: repo (string), description (string), stars (number), forks (number), open_issues (number), primary_language (string), last_updated (ISO 8601 string), url (string).'
• Add error recovery guidance: 'If GitHub API returns 404, the repository does not exist or is private. If 403, rate limit exceeded, retry after 60 seconds.'
• Constrain parameters: owner should match GitHub username pattern (alphanumeric, hyphens, no spaces); repo should be 1-255 chars. Add to parameter descriptions.
• Mention rate limit in tool description: 'Note: GitHub API allows 60 requests/hour per IP without authentication. Provide a GitHub token via environment variable to increase to 5000 req/hr.'
• Add readOnlyHint annotation to tool definition to signal idempotency and safe retry behavior to LLM.

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained