This server has 29 tools with significant definition gaps. Only 2 tools (get_code_scanning_alert, list_code_scanning_alerts) have visible input schemas with proper type definitions and descriptions. The remaining 27 tools lack visible schema definitions in the provided source, their schemas are inferred but not shown. Tool descriptions vary: get_me has a reasonable description (95 chars), but most others are missing or not visible. Parameter descriptions are sparse. No tool shows output schema documentation. Error handling is present in code (e.g., getMe checks HTTP status) but error messages lack recovery guidance. The server follows basic tool registration patterns but falls short of production-grade definition quality.

• Add explicit input schemas to all 27 undocumented tools. Each schema must include parameter types (string, number, boolean, array, object), required flags, and descriptions. Use the two code_scanning tools as a template.
• Write descriptions for all 27 tools following the pattern: WHAT does it do, WHEN to use it, WHAT it returns. Target 50 - 200 characters per description. Example: 'Get a GitHub issue by owner, repo, and issue number. Returns issue details including title, body, state, and assignee. Use this to fetch a specific issue before commenting or updating.'
• Document output schemas for all tools. Specify which fields are returned, their types, and which fields are needed for chaining to other tools (e.g., issue_id for add_issue_comment). Include pagination info (limit, offset, total_count) for list_* tools.
• Add tool annotations (readOnlyHint, destructiveHint) to all tools. Mark read-only tools with readOnlyHint=true; mark destructive tools (create_*, delete_*, merge_*, push_*) with destructiveHint=true. This helps clients apply appropriate safeguards.
• Enhance error messages with recovery guidance. Instead of 'failed to get user: <error>', return 'User not found. Try search_users() with a partial name, or check that the GitHub token has user:read scope.' This guides LLM retry logic.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry