Server has 6 tools with basic schemas and descriptions, but significant gaps limit production readiness. Weather tools (get-alerts, get-forecast) have proper Zod schemas with constraints and descriptions. NPC tools lack visible schema definitions in provided code, only inferred from parameter lists. Descriptions are present but generic (10-50 chars for most NPC tools), below the 50-200 char baseline for LLM optimization. No error handling guidance, no output schema documentation, no tool annotations. Tool composition is reasonable (single responsibility), but parameter naming lacks consistency (npcId vs state). No evidence of pagination, batching, or idempotent operation patterns.

• Expand NPC tool descriptions to 80-150 chars. Example: 'npc-move-to: Commands a specific NPC to move to a target position. Use this to navigate NPCs across the game world. Requires valid npcId and target coordinates {x, y, z}. Returns success/failure and final position.'
• Document output schemas for all tools. Example: 'get-alerts returns {alerts: [{event, area, severity, status, headline}], count: number}'. Weather tools should specify forecast structure.
• Add error handling guidance to descriptions. Example: 'If NPC not found, returns error 404 with message. Call npc-list-all to discover valid NPCs. If coordinates out of bounds, returns error 400 with valid range.'
• Add tool annotations (readOnlyHint, destructiveHint) to tool definitions. Mark npc-move-to and npc-interact-with as destructive; mark get-* tools as readOnly.
• Implement confirmation pattern for destructive NPC tools. Add optional 'dryRun' parameter to npc-move-to and npc-interact-with, or create separate confirm_npc_action tool.