Critical gaps across all 15 tools. While tool names follow verb_noun convention (objection-analyzer-*, outbound-nurture-*, audience-icp-*, outreach-icp-*, sales-nav-*), descriptions are minimal (10-50 chars, well below the 194-char baseline). Input schemas are visible but severely incomplete: most parameters lack type definitions beyond basic strings/objects/arrays. No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges, formats). Tools like objection-analyzer-purge (DESTRUCTIVE risk) lack confirmation patterns. No evidence of idempotency, pagination, or response field documentation. This server reads as a proof-of-concept with tool stubs rather than production-grade definitions.

• Expand every tool description to 50-200 chars. Include: what it does, when to call it, what it returns. Example: 'Analyze objection handling performance from a run JSON file. Returns success rate, top objections, and recommended playbook updates. Call after each sales cycle to refine objection responses.'
• Document output schemas for all tools. Specify field names, types, and descriptions. Example for objection-analyzer-analyze: {success_rate: number, top_objections: [{objection: string, frequency: int, recommended_response: string}], playbook_updates: array}
• Add nested schema definitions for object parameters. For 'spec' in audience-icp-filter-classify, define: {icp_criteria: {industry: [string], company_size: string, revenue_range: string}, leads: [{name: string, company: string, ...}]}
• Add parameter constraints: date fields use YYYY-MM-DD format with description 'ISO 8601 date'; numeric fields specify min/max (e.g. 'window: 1-365 days'); enums for categorical params (e.g. 'redact: true|false').
• Implement confirmation pattern for objection-analyzer-purge: add a 'dry_run' boolean param (default true) that returns count of records to be purged without deleting. Require explicit dry_run=false to execute.