Single tool 'search_products' has a clear action verb and reasonable description (156 chars), but lacks critical depth. Input schema is present with types and descriptions for both parameters, meeting baseline requirements. However, output schema is completely undocumented, the tool description mentions returning 'product name, price in TRY, stock status and product URL per market' but no structured output schema is visible in the code. The description lacks guidance on pagination, result limits, or error recovery. Parameter descriptions are adequate but could specify constraints (e.g., max query length, what 'in stock' means per market). No tool annotations (readOnlyHint, etc.) despite being READ_ONLY. Error handling is mentioned in features but not evident in tool definition.

• Add explicit output schema documenting the response structure: array of Product objects with fields {market: string, name: string, price: {available: boolean, amount?: number, currency: string}, stockStatus: enum, url: string}, plus metadata {resultCount: number, marketErrors: array}.
• Document pagination: specify max results per market (e.g., 20), whether offset/limit params are supported, and how to request additional pages.
• Add readOnlyHint: true to tool schema to signal this is a safe, cacheable, retry-safe operation.
• Formalize query parameter constraints: max 128 characters (already in code), min 1 character, and explain that special characters are URL-encoded.
• Add error recovery guidance: 'If a market returns no results, try a broader query or check market availability. If marketErrors is non-empty, some markets were unreachable, results are partial but usable.'
• Document 'only_in_stock' semantics: explain that stock status is market-specific and may be inferred from price availability or explicit stock indicators.