Server has 10 tools with complete input schemas and basic descriptions. All tools follow verb_noun naming (get_, list_, create_, update_, merge_, decline_). Schemas are properly typed with required fields. However, descriptions are generic (avg ~50 chars, well below the 194-char baseline for A+ tools) and lack context about when to use each tool, prerequisites, or recovery guidance. Parameter descriptions are minimal. No output schemas documented. Error handling is absent from visible code. Tool descriptions do not indicate state-modifying consequences (WRITE/IRREVERSIBLE risks). Missing pagination guidance for list tools.

• Expand tool descriptions to 100 - 200 chars. Include WHAT the tool does, WHEN to use it (vs. similar tools), and WHAT it returns. Example: 'Get detailed metadata for a repository including owner, visibility, default branch, and recent activity. Use this after list_repositories to fetch full details. Returns: repo_id, name, slug, is_private, description, owner, default_branch, created_at, updated_at.'
• Document output schemas for all tools. Specify returned fields, types, and which IDs/references chain to downstream tools. Example for get_repository: '{repo_id: string, name: string, slug: string, workspace_id: string, is_private: boolean, description: string, owner: {user_id: string, username: string}, default_branch: string, created_at: ISO8601, updated_at: ISO8601}'
• Add pagination to list_repositories and list_pull_requests: include 'limit' (default 20, max 100) and 'offset' (default 0) parameters. Return 'total_count' and 'has_more' in responses. Document in descriptions: 'Results are paginated; default limit is 20. Use offset to fetch additional pages.'
• Clarify state-modifying consequences in descriptions. For merge_pull_request: 'Merges a pull request and marks it as MERGED. This is irreversible, the PR cannot be reopened. Returns: merge_commit_sha, merged_at, merged_by. Consider calling get_pull_request first to verify the PR is ready.'
• Add error handling guidance to tool descriptions. Example for create_repository: 'If the repository already exists, returns 409 Conflict with message 'Repository already exists'. If workspace is invalid, returns 404 with 'Workspace not found, verify workspace ID via list_repositories.''