All 8 tools have basic descriptions and consistent naming (mw-*-fetch pattern), but critical gaps undermine quality. No input schemas are visible in the provided source code, only parameter names and enums are inferred from test files. Tool definitions appear to be registered elsewhere (not shown), making verification impossible. Descriptions are minimal (10-50 chars) and lack context on WHEN to use each tool or WHAT they return. No output schemas documented. Error handling and recovery guidance absent. The codebase shows a tool framework (ITool, ToolAvailability) but actual tool implementations are not provided.

• Document full JSON Schema for all tool inputs, including type, enum, minLength, maxLength, and pattern constraints. Provide schemas in the tool registration code, not just test files.
• Expand descriptions to 50-150 characters. Include: (1) what the tool does, (2) when to use it vs similar tools, (3) what it returns. Example: 'Fetch the player character's current attributes (health, magicka, fatigue, skills). Use this before planning combat or spell casting.'
• Document output schemas for all tools. Specify field names, types, and whether results are paginated. Example: 'Returns {items: [{id, name, quantity, weight}], total: number}'.
• Add parameter descriptions for mw-menu-fetch (output_mode) and mw-reference-fetch (scope, detail_level). Explain what each enum value produces and when to use it.
• Implement error recovery guidance in ToolAvailability. When a tool is unavailable, suggest which tool to call instead or what state change is needed. Example: 'Tool unavailable because player is in menu mode. Call mw-player-fetch to check game state, or wait for player to exit menu.'