Strong foundation with 15 well-named tools following verb_noun convention (acquire_leadership, kv_put, lease_renew). All tools have descriptions (avg 180 chars, within 10-1024 baseline). Input schemas present for all tools with typed parameters. However, output schemas are not documented, LLMs cannot predict return structures. Parameter descriptions are present but terse (avg 45 chars vs 72 baseline). Missing error recovery guidance and confirmation patterns for destructive operations (kv_delete, lease_release). No tool annotations (readOnlyHint, destructiveHint) despite clear risk classifications in metadata.

• Document output schemas for all 15 tools. Specify return types (e.g., node_info returns {node_id: string, address: string, port: u16}; kv_get returns {value: bytes, ttl_remaining_ms: u64 | null}). Use JSON Schema format.
• Add tool annotations to schema: mark kv_delete, lease_release, kv_put as destructiveHint=true; mark kv_get, list_peers, watch_peers as readOnlyHint=true; mark kv_put_if_absent as idempotentHint=true.
• Expand parameter descriptions to 60-100 chars with format/constraint details. Example: 'Lease handle (opaque pointer from acquire_leadership/acquire_lock; valid until expiry or explicit release)' instead of 'Opaque lease handle from acquire'.
• Add recovery guidance to error cases. Example for try_acquire_lock: 'Returns Ok(None) if lock held by another session, retry after exponential backoff or call watch_peers to detect session release.'
• Implement dry-run or confirmation pattern for kv_delete and lease_release. Add optional 'confirm: bool' parameter or separate 'confirm_kv_delete' tool to prevent accidental data loss.

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

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