Four tools with complete Zod schemas and basic descriptions. All tools follow verb_noun naming (people-also-ask, google-autocomplete, forums, semantic-keywords). Schemas include proper type constraints (minLength, length, defaults). However, descriptions are generic (34-56 chars, below the 50-200 char LLM-optimized baseline) and lack context about WHEN to use each tool or what distinguishes them. Parameter descriptions are present but minimal. No output schema documentation. Error handling returns plain text without recovery guidance. No pagination support despite tools returning lists. Missing idempotency hints for read-only operations.

• Expand tool descriptions to 80-150 chars. Include WHEN to use (e.g., 'Use for discovering related search terms that users actually search for') and HOW it differs from similar tools (e.g., 'Unlike google-autocomplete, this returns nested question hierarchies').
• Document output schema for each tool. Specify that results are arrays of strings, include field names (questions, suggestions, keywords), and note any metadata (count, source).
• Add limit and offset parameters to all tools. Cap default results at 20-50 items and document the limit in the tool description per mxe:enforce-result-limits.
• Improve error messages to guide recovery. Instead of 'Failed to retrieve data', return 'API error: invalid language code. Supported codes: en, fr, es, de. Retry with a valid code.' or 'API rate limit exceeded. Retry in 60 seconds.'
• Add readOnlyHint: true to all tool definitions to signal to clients that these are safe, idempotent read operations with no side effects.