Four tools with complete Zod schemas and Turkish descriptions. All tools are read-only search/list operations with proper parameter validation (min/max on limit). Naming follows verb_noun pattern (search_*, get_*, list_*). Descriptions are substantive (100-200 chars) and explain data source and result format. However, output schemas are not formally documented, responses are JSON.stringify'd without explicit field definitions. Parameter descriptions are good but lack format guidance (e.g., no regex for slug format). No error recovery guidance in descriptions. Missing tool annotations (readOnlyHint) despite all being read-only.

• Add explicit output schema documentation to each tool. Define fields returned (e.g., name: string, slug: string, rating: number, reviews_count: integer, url: string) so LLMs know what to extract.
• Add readOnlyHint: true to all four tool definitions via registerTool options to signal safety to agents.
• Enhance slug parameter description: 'Lowercase hyphenated slug from search results (e.g., a101-mersin-turunclu). Validate format before passing.'
• Add recovery guidance to get_company_details error response: 'Company not found. Try search_companies() with the business name or category to find the correct slug.'
• Return total_count and next_cursor in search responses to enable pagination. Modify response structure: { results: [...], count: N, total_count: M, next_cursor: '...' }