Server has 17 tools with complete input schemas and descriptions. Naming follows verb_noun convention (create_issue, list_issues, etc.). Descriptions are present but brief (avg ~50 chars, below the 194-char baseline). Parameters have types and descriptions, but lack enums for constrained values (e.g., 'state' accepts 'open|closed|all' but not declared as enum). Output schemas are not documented. Error handling and recovery guidance are absent. No tool annotations (readOnlyHint, destructiveHint) despite clear risk levels (WRITE, DESTRUCTIVE, READ_ONLY). Missing pagination details for list_* tools.

• Add output schemas to all tools. Document return type (object with fields: issue_id, issue_url, issue_number, state, created_at, etc.). Use JSON Schema format.
• Convert constrained parameters to enums. E.g., 'state' → enum: ['open', 'closed', 'all']; 'data_type' → enum: ['TEXT', 'SINGLE_SELECT', 'DATE', 'NUMBER', 'ITERATION'].
• Expand descriptions to 100 - 200 chars. Include WHEN to use, WHAT it returns, and any prerequisites. E.g., 'Create a GitHub issue in a repository. Returns issue_id, url, and state. Requires GH_TOKEN with repo:write scope.'
• Add tool annotations via fastmcp. Mark read-only tools with readOnlyHint=true; destructive tools (delete_*) with destructiveHint=true; idempotent tools with idempotentHint=true.
• Document pagination for list_* tools. Specify default limit (e.g., 20), max limit (e.g., 100), and how to fetch next page (offset/cursor). E.g., 'Returns up to 20 issues. Use offset parameter to fetch next page.'