This server has 14 tools with basic schemas and minimal descriptions. All tools have input schemas with type definitions and required fields, which is positive. However, descriptions are extremely brief (10-30 chars), falling well below the 50-200 char baseline for LLM-optimized tools. Parameter descriptions are almost entirely absent, only tool-level descriptions exist. No output schemas are documented. Error handling is not visible in the provided code. The server lacks tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite having tools with clear risk profiles (DESTRUCTIVE, WRITE, READ_ONLY). Tool names follow verb_noun convention (create_repo, list_branches, delete_file), which is good, but the minimal descriptions and missing parameter guidance severely limit LLM reasoning quality.

• Expand all tool descriptions to 50-200 characters. Example: 'create_repo' should be 'Create a new GitHub repository under the authenticated user or specified owner. Returns the repository URL and clone commands.' instead of 'Crear repositorio en GitHub'.
• Add descriptions to every parameter. For 'owner', write 'GitHub username (optional; defaults to authenticated user)'. For 'repo', write 'Repository name (required)'. For 'path', write 'File path within the repository (optional; defaults to root)'.
• Document output schemas for each tool. Example for list_repos: 'Returns {repositories: [{name, url, description, is_private, created_at}], total_count, next_cursor}'.
• Add tool annotations to the MCP tool definitions. Mark delete_* tools with destructiveHint=true, create_* and merge_pr with idempotentHint=false (since they have side effects), and list_* with readOnlyHint=true.
• Implement and document error handling. Return structured errors like '{error: "repo_not_found", message: "Repository 'xyz' not found. Available repos: [list]", recovery: "Try list_repos() to see available repositories"}' instead of generic failures.