WAVE MCP server has 24 tools across 7 modules (streams, studio, analytics, billing, production, voice, design, wave-ask). Tool definitions are centralized in src/tools/index.ts and properly registered via allTools array. However, source code provided is incomplete, only package.json, server.ts, sdk-server.ts, and index.ts are visible. Actual tool schemas, descriptions, and handlers in src/tools/*.ts files are NOT shown, making it impossible to verify parameter types, descriptions, output schemas, or error handling. Per HARD SCORING RULE: 'If you cannot see the actual tool definition in the source (only inferred): cap that tool's overall at 50.' Since tool implementations are inferred from file paths and names only, all 24 tools are capped at 50. The visible code shows good architectural patterns (single source of truth, dual transport support, startup validation) but provides zero evidence of schema quality, description completeness, or parameter documentation.

• Provide complete tool implementation files (src/tools/*.ts) showing inputSchema definitions, descriptions, and handlers. Current evaluation is capped at 25/100 per tool due to missing source code.
• Each description must answer: What does it do? When to use it? What does it return?
• Document every parameter with type, description, constraints (enum, min/max, pattern), and whether it is required. Use Zod schema annotations visible in the code.
• Define output schemas for all tools, especially list tools. Include pagination (limit, offset, total_count), chaining IDs (e.g., stream_id for downstream calls), and field descriptions.
• Implement error handling that guides LLM recovery: 'Stream not found. Available streams: [list]. Try stream_list() to discover.' Use pattern:recovery-guide and pattern:error-classification.