Critical gaps across all dimensions. Tool definitions are inferred from Python source (iching_mcp/server.py) rather than explicitly visible in Rust MCP registration. Descriptions are present but minimal (10-80 chars, well below 50-200 char baseline for LLM optimization). Input schemas visible in Python but lack type definitions and constraints, parameters are documented as arrays/strings with minimal guidance on structure, format, or valid values. No output schemas documented. No error handling guidance. No parameter validation rules or dependency documentation. The Rust HTTP server (ga-semantics-mcp) has no visible tool definitions in provided source, only Cargo.toml and Dockerfile. Python tools appear to be a separate implementation not integrated into the Rust MCP server.

• Explicitly register all 6 tools in the Rust MCP server with full JSON Schema input definitions including type, description, enum/pattern constraints, and min/max bounds for each parameter.
• Expand tool descriptions to 50-200 characters following LLM-optimization guidelines: state WHAT the tool does, WHEN to use it instead of similar tools, and what it returns. Example: 'Evaluate Clifford algebra Cl(3) operations on blades and rotors. Use this to compute geometric transformations and verify blade algebra identities. Returns computed results with operation trace.'
• Document output schemas for all tools. Specify return type (object/array), required fields, field types, and field descriptions. Include IDs and references needed for downstream tool chaining.
• Add parameter validation rules to descriptions: format (regex/ISO8601), range (min/max), enum values, and dependencies. Example: 'ops: Array of operation objects. Each object must have {type: string (one of: multiply, wedge, dot), operands: array of 2-3 blade strings}.'
• Implement error handling with recovery guidance. Categorize errors as retryable/user-fixable/fatal and provide actionable next steps. Example: 'Invalid blade notation: got "e123x", valid blades are e0, e1, e2, e3, e12, e13, e23, e123. Try again with corrected notation.'