KommoMCP has 12 tools with reasonable naming (verb_noun pattern) and basic schemas. However, critical gaps undermine quality: (1) Parameter descriptions are sparse or missing entirely, e.g., kommo_leads_list has 10 parameters but many lack descriptions (created_at_from, created_at_to lack format guidance); (2) Tool descriptions are present but generic and under-optimized for LLM selection, e.g., 'Get list of leads with filtering' does not explain WHEN to use this vs kommo_leads_summary; (3) Output schemas are not documented anywhere in the source, LLMs cannot plan downstream calls without knowing what fields are returned; (4) Error handling is absent, no guidance on retryability, user-fixable errors, or recovery paths; (5) No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (WRITE vs READ_ONLY). Naming is solid (kommo_ping, kommo_sync_start, kommo_leads_list follow verb_noun), but descriptions lack the 50 - 200 char LLM-optimized range and parameter-level guidance. Schemas are present in input but incomplete (missing type info for some fields, no output documentation).

• Document output schemas for all 12 tools. Include field names, types, and whether fields are always present or conditional. Example: kommo_leads_list should return {leads: [{id, name, status_id, pipeline_id, responsible_user_id, created_at, updated_at}], total_count, page, limit}.
• Expand parameter descriptions to include format constraints. For date parameters (created_at_from, created_at_to, date_from, date_to), specify 'ISO 8601 format (YYYY-MM-DD)' or 'Unix timestamp in seconds'. For enums (order_dir, method), list valid values inline.
• Rewrite tool descriptions to be LLM-optimized (50 - 200 chars) and answer: What does it do? When should I call it instead of a similar tool? Example: 'List all leads with optional filtering by pipeline, stage, or owner. Use this for detailed lead data; use kommo_leads_summary for a quick count without loading full records.'
• Add error handling guidance. Document which errors are retryable (network timeout, rate limit) vs user-fixable (invalid pipeline_id) vs fatal. Example: 'If pipeline_id is invalid, call kommo_pipelines_list to discover valid IDs.'
• Add tool annotations to the MCP server registration. Mark kommo_sync_start with destructiveHint=true (modifies state). Mark all READ_ONLY tools with readOnlyHint=true. Mark idempotent tools (kommo_ping, kommo_leads_list) with idempotentHint=true.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry