Tuteliq MCP has 14 tools with solid naming conventions (all verb-prefixed: list_, create_, update_, delete_, test_, get_, analyze_, generate_). Descriptions are present for all tools and range from adequate to comprehensive. However, there are significant gaps in input schema completeness, parameter descriptions, and output schema documentation. All tools have descriptions ≥20 characters, which prevents hard cap violations. The analyze_emotions and get_action_plan tools have the most detailed parameter descriptions and complex schemas. Several tools (especially admin tools like test_webhook, regenerate_webhook_secret) lack detailed parameter descriptions. No explicit output schemas are documented in the provided source code. Error handling guidance is not evident from tool definitions.

• Document output schemas for all 14 tools. For example: list_webhooks should return {webhooks: [{id, name, url, events, headers, is_active, created_at}], total_count}. get_pricing should return {plans: [{name, features, rate_limits}]}.
• Expand descriptions for low-scoring tools. get_pricing_monthly currently states 'Monthly Usage', rewrite as 'Retrieve monthly usage statistics aggregated across your account. Returns total requests, breakdown by tool, and per-day trends for the current month.'
• Add JSON Schema constraints for parameters. For get_usage_history, add minimum: 1, maximum: 30 to 'days' parameter. For get_usage_by_tool, add pattern: '^\d{4}-\d{2}-\d{2}$' to 'date' parameter.
• Add error recovery guidance to tool descriptions. E.g., 'delete_webhook: Returns 404 if webhook ID not found. Try list_webhooks() to verify the ID exists.' or 'regenerate_webhook_secret: May fail if the webhook is being deleted. If so, the secret is already invalidated.'
• Implement confirmation/dry-run for destructive operations. Add an optional 'confirm' parameter to delete_webhook and regenerate_webhook_secret, or document in the description: 'Call with dry_run=true to preview the change before confirming.'
• Clarify mutual exclusivity in analyze_emotions. Rewrite parameter descriptions: 'content' (string, required if messages not provided) and 'messages' (array, required if content not provided). Mark exactly one as required in schema.
• For create_webhook and update_webhook, document what 'events' array accepts. E.g., events: {type: 'array', items: {enum: ['message.created', 'message.updated', 'message.deleted', ...]}, description: 'Event types to subscribe to...'}