Strong foundation with 11 well-named tools following verb_noun convention (who_am_i, list_projects, get_issue, create_issue, add_issue_note). All tools have descriptions and input schemas with proper JSON Schema types. Tool base class implements permission gating, schema validation, and error handling. However, 9 of 11 tools lack visible parameter descriptions in the provided source, only create_issue and add_issue_note show full schemas with descriptions. Output schemas are not documented. Error handling is present but recovery guidance is minimal. Pagination support exists (paged helper) but not all list tools show limit/offset parameters in visible schemas.

• Add parameter descriptions to all 9 tools lacking visible schemas. Each parameter (project_id, limit, offset, query, etc.) must have a description explaining what it controls, valid range, and format. Reference the create_issue schema as a model.
• Document output schemas for all tools. Add an outputSchema field to the descriptor() method showing the structure of responses (e.g., {type: 'object', properties: {id, name, description, ...}, required: [...]}).
• Enhance error messages with recovery hints. When a project is not found, suggest 'Try list_projects() to see available projects.' When permission is denied, suggest 'Check your OAuth scopes or contact the administrator.'
• Verify pagination parameters are declared in all list tool schemas. Ensure limit and offset are present with min/max constraints (e.g., limit: 1-100, offset: 0+) and that the paged() envelope is used consistently.
• Add per-tool examples in descriptions. For create_issue, note: 'Creates a new issue in a project. Returns the issue ID for use with add_issue_note() or get_issue().' This guides chaining.

Inferred effective spec: 2026-07-28+.

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained