Critical failures across all dimensions. Tool definitions are found only in test code (FakeMcpServer.cs), not in production server implementation. Descriptions are minimal ('Read a file.' / 'Write a file.', 12-13 chars, well below 20-char minimum). No visible input schemas, parameter descriptions, or output documentation. Tools appear to be inferred from test fixtures rather than explicitly registered in the actual MCP server. This is a non-functional evaluation baseline.

• Move tool definitions from test code into the production MCP server implementation with explicit registration (e.g., via McpServer.AddTool() or equivalent).
• Expand descriptions to 50-200 characters. Example: 'read_file: Read and return the contents of a file at the specified path. Returns file content as text or binary. Fails if file does not exist or is not readable.'
• Define complete input schemas with parameter types, descriptions, and constraints. Example: { 'path': { 'type': 'string', 'description': 'Absolute or relative file path (max 1024 chars)' }, 'encoding': { 'type': 'string', 'enum': ['utf-8', 'ascii'], 'default': 'utf-8' } }
• Document output schemas. Example for read_file: { 'content': 'string', 'size_bytes': 'integer', 'encoding': 'string', 'last_modified': 'ISO 8601 timestamp' }
• For write_file, add a dry_run parameter and document idempotency. Include error guidance: 'Path does not exist. Create parent directories first with mkdir, or check the path spelling.'