Critical failure: Cannot verify ANY tool definitions in source code. The repository provides NO visible tool schemas, parameter definitions, or descriptions in the supplied code excerpt. Tool names exist in config files and package.json, but actual tool registration code (which should define schemas, parameter types, descriptions, and input validation) is absent from the provided source. The Dockerfile references 'src/stdio-server.ts' but that file's content is not included. Without access to the actual tool implementation, all schemas and detailed descriptions remain unverifiable. The brief descriptions in the TOOLS list ('Multi-year ISO/AMT optimization calculator', etc.) are generic and under 50 characters, well below the 194-char baseline for production tools. No parameter schemas, input validation, or error handling guidance visible. This violates multiple hard rules: cannot confirm schemas exist, descriptions are too short, and tool registration code is not in the supplied source.

• CRITICAL: Provide complete tool definitions including input_required schemas with parameter type definitions, constraints, enums, and per-parameter descriptions. Current descriptions are 40-50 chars; expand to 150-300 chars with context on WHAT the tool does, WHEN to use it, and expected output.
• Rename tools to start with action verbs: iso_amt → calculate_iso_amt, nso → analyze_nso_decision, rsu → evaluate_rsu_vesting, qsbs → check_qsbs_qualification, concentration → analyze_stock_concentration, protective_put → price_protective_put, equity_funding → calculate_equity_funding, collar → price_collar.
• Document output schemas showing all returned fields, their types, and purposes. Indicate whether results are paginated and how to handle large result sets.
• Add comprehensive parameter descriptions with format hints, constraints, and valid ranges. E.g., 'grant_date: ISO 8601 date string (YYYY-MM-DD) when the stock options were granted'.
• Implement error handling that returns recovery guidance. E.g., 'Invalid equity type. Must be one of: iso, nso, rsu, qsbs. See documentation for definitions.'
• Verify tool composition: ensure tools that depend on each other's outputs (e.g., calculating tax impact → evaluating concentration) return IDs and data structures that match downstream parameter names.
• Add security considerations: confirm that tool parameters do not expose API keys or secrets, and that responses do not include tokens or internal credentials that would leak into LLM context.