Server has 6 tools with complete input schemas and descriptions. Naming follows verb_noun convention (search_, generate_, analyze_, trending_, commission_). However, descriptions lack specificity about when to use each tool vs. alternatives, parameter descriptions are minimal, and output schemas are entirely undocumented. No error handling guidance. Tools are read-only but lack explicit annotations. Missing details on API dependencies, rate limits, and failure modes.

• Document output schema for each tool. E.g., search_products should specify: returns array of {product_id, title, price, image_url, commission_rate, estimated_earnings}, with total_count and next_cursor for pagination.
• Add parameter descriptions explaining format constraints. E.g., 'category: Category ID in format MLBXXXX (e.g., MLB1051 for phones). See Mercado Libre category list for valid IDs.'
• Add tool annotations to schema: set readOnlyHint: true for all tools since they perform no mutations.
• Expand tool descriptions to include when to use each tool. E.g., 'Use search_products to find specific items by keyword. Use trending_products to discover high-velocity items in a category without a specific search term.'
• Add error handling guidance to descriptions. E.g., 'If product_id is invalid, returns error with available product IDs. If API rate limit exceeded, retry after 60 seconds.'