Server has 5 tools with complete Zod schemas and basic descriptions. All tools are properly registered with input validation. However, descriptions are minimal (10-20 chars), lack context on WHEN to use each tool, and do not explain consequences of write operations. Parameter descriptions are present but generic. No output schema documentation. Error handling returns raw API messages without recovery guidance. Missing idempotency hints on write tools and no confirmation patterns for destructive operations.

• Expand tool descriptions to 50-150 chars. Example: 'add_pr_reviewers: Request code review from GitHub users on an existing PR. Idempotent, safe to retry. Returns updated reviewer list.' This tells LLM WHAT, WHEN, and CONSEQUENCE.
• Add idempotentHint and destructiveHint annotations to tool definitions. Mark write operations with destructiveHint=true so agents know to confirm before executing.
• Document output schemas explicitly. Return structured JSON with fields like {success: bool, pr_number: int, reviewers: string[], message: string} instead of plain text.
• Enhance error messages with recovery guidance. Instead of 'Error: Not Found', return 'PR #123 not found in owner/repo. Verify owner, repo, and pull_number are correct. Call list_prs to find valid PR numbers.'
• Add format constraints to parameter descriptions. Example: 'reviewers: array of GitHub usernames (alphanumeric, 1-39 chars, no spaces). Example: ["alice", "bob-dev"]'.