Four tools with complete input schemas and basic descriptions. All tools are READ_ONLY and follow verb_noun naming (search, get_page, pages_by_name, hierarchy). However, descriptions are terse (10-80 chars, below the 50-200 char baseline for LLM optimization), lack context on WHEN to use each tool, and parameter descriptions are minimal. No output schema documentation. Error handling exists but lacks recovery guidance. Missing tool annotations (readOnlyHint). No pagination support despite search potentially returning large result sets.

• Expand tool descriptions to 80-150 chars. Example: 'search: Search EOL by common or scientific name. Returns page IDs and basic info. Use pages_by_name for exact scientific name matching, or get_page to fetch full details by ID.'
• Document output schemas inline or in comments. E.g., 'search returns {results: [{id, name, rank, ...}], total_results}' so LLMs know what fields to extract.
• Add readOnlyHint: true to all tool schemas to signal safety: inputSchema: {type: 'object', properties: {...}, readOnlyHint: true}
• Replace limit description text with JSON Schema constraints: {type: 'number', minimum: 1, maximum: 50, default: 10}. Same for detail: {type: 'boolean', description: 'Include images and text data objects. Default: false.'}
• Enhance error messages with recovery hints. E.g., 'EOL page not found. Verify the page ID from search() or pages_by_name() first.' or 'Invalid query format. Try a scientific name like "Panthera leo" or common name like "lion".'