Server has 5 tools with basic descriptions and input schemas, but critical gaps undermine quality. Tool names lack action verbs (chat, configure, reset, clear_cache, models). Descriptions are present but generic (10-50 chars for most). Input schemas exist but lack proper type definitions and parameter descriptions. The 'configure' tool is dangerously vague, no enum for 'setting' parameter, no validation guidance. Error handling is absent from visible code. No output schemas documented. Composition is poor: 'configure' conflates viewing and changing settings; 'reset' and 'clear_cache' are similar concerns. No evidence of idempotency, pagination, or recovery guidance.

• Rename tools with action verbs: 'chat' → 'send_message', 'configure' → 'get_config' + 'update_config', 'reset' → 'clear_history', 'clear_cache' → 'clear_response_cache', 'models' → 'list_models'.
• Split 'configure' into two tools: get_config(setting: string) returns current value; update_config(setting: string, value: string) changes it. Add enum for 'setting' with valid options: model, api_key, region, provider.
• Document output schemas for all tools. E.g., 'chat' returns {message: string, model: string, tokens_used: number}; 'models' returns {models: [{name: string, provider: string, available: boolean}], total: number}.
• Add parameter descriptions and constraints. E.g., 'model' param: 'Optional model override (e.g., gpt-4o, claude-opus-4.6). If not specified, uses configured default.' Add 'provider' enum: [azure, openai, anthropic, google, digitalocean, bedrock, puter].
• Add error handling guidance. E.g., 'chat' description: 'If API key is invalid, call update_config(api_key, <new_key>). If model is unavailable, call list_models() to see alternatives.'