Three tools with basic schemas and Spanish descriptions. All tools have input schemas with types and required flags, but parameter descriptions are almost entirely missing (null values visible in schema). Tool descriptions are present but minimal (10-50 chars). No output schemas documented. No error handling guidance. No tool annotations (readOnlyHint/destructiveHint). Idempotency is implemented server-side but not declared in tool metadata.

• Add non-empty descriptions to every parameter. For 'operation_id', expand from 'UUID idempotente; el mismo id no crea duplicados' to include format (UUID v4), when to use (always for idempotent operations), and example. For 'stage', replace description with enum constraint and explain valid values.
• Document output schemas for all three tools. E.g., crm.create_contact returns Contact{id, email, first_name, last_name, phone?, company?, created_at}. Include field types and which fields are required vs. optional.
• Add tool annotations: mark crm.create_contact and crm.update_deal_stage with destructiveHint=true; mark crm.create_contact with idempotentHint=true (operation_id makes it safe to retry).
• Expand tool descriptions to 100-200 chars. E.g., crm.create_contact: 'Creates a new contact in the workspace CRM. Idempotent via operation_id, same ID never creates duplicates. Returns the created Contact with id, email, name, phone, company, and created_at timestamp.'
• Implement structured error responses with recovery hints. E.g., if stage is invalid, return: {error: 'Invalid stage: got "pending", must be one of: prospecting, qualified, proposal, won, lost'}. For search_contacts, document limit bounds (1-100) and default (20).

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

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