Five tools with acceptable naming (verb_noun structure) and present schemas. Descriptions are adequate but brief (18-70 chars). All parameters have type definitions and descriptions. Zod schemas provide runtime validation. However, critical gaps exist: no output schema documentation, no error guidance for recovery, no parameter value ranges/constraints, and missing natural identifiers (e.g., accepting usernames alongside IDs). The tools follow basic patterns but lack the production-grade polish expected for A-grade servers. Response handling is minimal (JSON stringification with no field documentation).

• Document output schemas for all tools. For get_my_qiita_articles, specify: 'Returns array of objects with fields: id (string), title (string), url (string), tags (array of {name, versions}), created_at (ISO8601), updated_at (ISO8601). Paginated: use page/per_page to iterate.'
• Add error recovery guidance. Replace generic error handling with specific messages: 'API token not set. Set QIITA_API_TOKEN environment variable.' or 'Article not found. Verify item_id matches an existing article.'
• Add constraints to numeric parameters. Update get_my_qiita_articles schema: page: z.number().min(1).max(999999), per_page: z.number().min(1).max(100)
• Expand tool descriptions to 50-200 characters and include WHEN clause. Example: 'Fetches paginated list of articles authored by the authenticated user. Call this first to see your article inventory before updating or searching for specific content.'
• Document item_id format in parameter descriptions. Example: 'The ID of the Qiita article to fetch (alphanumeric string, ~16 chars, e.g., abc123def456ghij).'
• Add pre-execution confirmation for post_qiita_article and update_qiita_article. Implement a dry-run mode or return a confirmation request with MRTR (Multi Round-Trip Request) requiring user approval before committing.
• Add tool annotations in server registration. For write tools: server.tool(name, description, parameters, handler, { destructiveHint: true }). For read tools: { readOnlyHint: true }.
• Validate QIITA_API_TOKEN at each tool call, not just at service construction. Return actionable error: 'QIITA_API_TOKEN not configured. Please set the environment variable and retry.'