This server has critical definition gaps. Tool descriptions are present but vague (e.g., 'Extract and collect one lead qualificatino field' contains a typo and lacks actionable context). Input schemas exist but lack depth: parameters have minimal descriptions, no enums for constrained values, and no output schemas documented. The 'lead' parameter in crm-sync-agent is typed as 'object' with only a generic description, no structure, required fields, or examples. Error handling is minimal (generic catch-all). No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk profiles (WRITE operations). Naming is acceptable but not verb-forward (lead-qualifier, crm-sync-agent, clear-session lack clarity on what 'lead-qualifier' returns or how it differs from a full qualification flow).

• Fix typo and expand lead-qualifier description to ~100-150 chars: 'Extract one BANT qualification field (budget, authority, need, timeline) from the user message. Returns {field, value, confidence_score}. Call sequentially to build a complete lead profile.'
• Define crm-sync-agent 'lead' parameter as a structured object schema with required fields (e.g., budget, authority, need, timeline, email, company) and types. Document which fields are optional.
• Add output schemas to all tools. E.g., lead-qualifier returns {type: 'object', properties: {field: string, value: string, score: number}}. crm-sync-agent returns {type: 'object', properties: {success: boolean, lead_id: string, synced_at: string}}.
• Add tool annotations: lead-qualifier with readOnlyHint=true; crm-sync-agent and clear-session with destructiveHint=true. Optionally add idempotentHint=true to clear-session if clearing an already-cleared session is safe.
• Enhance error messages with recovery guidance. E.g., 'Failed to extract field from message. Ensure the message directly answers the question: {lastPromptedQuestion}. Try rephrasing or ask the user to clarify.'