Critical gaps across all dimensions. Tool definitions are inferred from main.go switch statement rather than explicitly registered with schemas. No input schemas visible in source code, all 8 tools lack documented parameter types and constraints. Descriptions are present but generic (10-80 chars, well below 50-200 char LLM-optimized baseline). No output schemas documented. No error handling guidance. No parameter validation rules. Tool names lack verb-noun clarity (e.g., 'invoke' is vague; 'invoke_agent' would be clearer). No evidence of idempotency, pagination, or composition patterns. Security concerns: FD_LIVE_KEY and GITHUB_TOKEN exposed as environment variables rather than server-side injection.

• Add explicit MCP tool registration with full JSON Schema for all parameters. Include type, description, enum constraints, and min/max bounds for each parameter.
• Document output schemas for all tools. Specify return fields, types, and structure so LLMs can plan chaining and extraction.
• Expand tool descriptions from current 10-80 chars to 50-200 chars. Include WHAT the tool does, WHEN to use it, and any prerequisites (e.g., 'Requires FD_LIVE_KEY with positive balance').
• Implement server-side secret injection. Move FD_LIVE_KEY and GITHUB_TOKEN from environment variables to secure vault/config, never expose in tool parameters or responses.
• Add error handling guidance. Return structured errors with error codes, human-readable messages, and recovery hints (e.g., 'auth_required: Set FD_LIVE_KEY environment variable').