All 15 tools suffer from severely underdeveloped schemas and descriptions. Every tool accepts a single generic 'input' parameter of type string with minimal guidance ('Input data (JSON)'), forcing LLMs to guess JSON structure. Descriptions are 2 - 5 words, far below the 10 - 1024 character baseline and insufficient for tool selection. No output schemas documented. Tool names lack action verbs (e.g., 'cashflow_forecast' vs 'forecast_cashflow'). No parameter validation, error handling guidance, or composition support. This is a wrapper around an external API with minimal MCP-specific design.

• Expand each tool description to 50 - 150 characters. Example: 'forecast_cashflow: Project cash inflows and outflows over a specified period. Requires: starting_balance, monthly_inflows (array), monthly_outflows (array), forecast_months (1 - 60). Returns: month-by-month balance, cumulative flow, and risk flags.'
• Replace the generic 'input' parameter with domain-specific, typed parameters. Example for cashflow_forecast: {starting_balance: {type: 'number', description: 'Initial cash balance in USD'}, monthly_inflows: {type: 'array', items: {type: 'number'}, description: 'Monthly inflow amounts'}, forecast_months: {type: 'integer', minimum: 1, maximum: 60, description: 'Number of months to forecast'}}.
• Document output schemas for each tool. Example: 'forecast_cashflow returns {months: [{month: number, balance: number, inflow: number, outflow: number}], total_inflow: number, total_outflow: number, final_balance: number, risk_flags: [string]}'.
• Rename tools to verb_noun pattern: cashflow_forecast → forecast_cashflow, working_capital_calc → calculate_working_capital, roi_calculator → calculate_roi, etc. This enables LLMs to parse intent from the name alone.
• Add error handling that returns actionable guidance. Example: if the API returns 400, parse the error and return {status: 'error', code: 'invalid_input', message: 'Missing required field: starting_balance', suggestion: 'Provide starting_balance as a number in USD'}. Classify errors as retryable (network timeout) vs. user-fixable (missing field) vs. fatal (auth failure).