Server defines 6 tools with basic schemas and descriptions in Spanish. All tools have input schemas with type definitions and descriptions present. However, descriptions are minimal (avg ~60 chars, below the 194-char baseline), lack context on WHEN to use each tool, and do not explain state-modifying consequences. Parameter descriptions are present but terse. Output schemas are not documented. Error handling is absent from tool definitions. Tool naming follows verb_noun convention (get_, add_, update_) which is good, but composition could be improved, update_prices and get_alerts are tightly coupled concepts that might benefit from clearer separation.

• Document output schemas for all 6 tools. Specify field names, types, and whether results are paginated. Example: get_products_list should return {products: [{id, nombre, precio_actual, precio_objetivo, url}], total_count, next_cursor}.
• Expand tool descriptions to 100 - 200 chars. Add WHEN context: 'Use get_alerts to find products below target price and trigger notifications. Call after update_prices completes.' State side effects: 'add_product creates a new tracking record and initiates first price scrape.'
• Add error handling guidance to descriptions. E.g., 'If product not found, returns error with available product names. Retry with search_products() if needed.'
• Clarify parameter relationships in get_product_price: 'Provide either product_id (exact match, faster) or product_name (partial search). If both provided, product_id takes precedence.'
• Add constraints to precio_objetivo: 'Optional numeric value in USD. If provided, must be > 0. Omit to disable price alerts for this product.'