manifoldbt-mcp exposes 14 tools with complete JSON schemas and descriptions. Naming follows verb_noun convention (get_version, list_indicators, run_backtest). Descriptions are present but generic, most lack context on WHEN to use each tool or dependencies between them. Parameter descriptions exist but are minimal (avg ~40 chars vs. baseline 72). Output schemas are not documented; callers must infer structure from code. Error handling is absent, no recovery guidance or actionable error messages. Security: license_key is exposed as a parameter (pattern:secret-injection violation). Composition is reasonable: tools are single-purpose, but no pagination on list_* tools and no batch variants despite agents likely calling run_backtest repeatedly.

• Move license_key to server-side configuration (environment variable or config file). Remove activate_license parameter from tool signature. Document in README how to set license via env var.
• Document output schemas for all run_* and plot_* tools. Include example JSON responses showing metrics, manifest, trade_count, warnings structure. Specify which fields are always present vs. optional.
• Add error handling descriptions to run_backtest, run_sweep, build_strategy: 'Returns error if strategy_code has syntax errors (e.g., undefined indicator). Returns error if config dates are invalid. Retryable: yes.'
• Enhance tool descriptions with decision trees: 'Use run_sweep for 1D parameter optimization. Use run_sweep_2d for 2D heatmap visualization. Use run_stability for robustness testing across market regimes (Pro).'
• Add limit and offset parameters to list_indicators and list_examples. Return {items: [...], total: N, has_more: bool}. Cap results at 50 items per page.