Strong foundation with 10 well-named, read-only tools covering OSRS Wiki queries. All tools have descriptions (avg 85 chars) and complete input schemas with type definitions and parameter descriptions. Output schemas are documented via Zod validators. Naming follows verb_noun pattern consistently (search_wiki, get_wiki_page, find_shop, etc.). However, descriptions are terse (under 100 chars) and lack dependency hints or recovery guidance. Error handling exists but is minimal, no actionable recovery paths for common failures like 'item not found'. Tool composition is sound (single responsibility, proper chaining via IDs), but descriptions could better explain WHEN to use each tool vs alternatives (e.g., get_item_sources vs find_shop).

• Expand tool descriptions to 150 - 250 chars. Add WHEN-to-use guidance: 'Use get_item_sources for a quick overview (up to 20 per category); use find_shop for complete paginated results.' This disambiguates overlapping tools.
• Add recovery hints to descriptions: 'If item not found, try search_wiki() with a partial name or check spelling.' This guides LLM error handling.
• Enhance parameter descriptions with format details: 'Search query (1-256 chars, supports partial matches; case-insensitive)' and 'Limit (1-100, default 10; higher values may timeout).'
• Implement tool annotations in server.ts: mark all tools with readOnlyHint=true and idempotentHint=true. This enables client-side caching and safe retries.
• Add a SERVER_INSTRUCTIONS note about pagination: 'For large result sets, use limit and offset parameters. Results are capped at 100 per page; check nextOffset for more data.' This is already in code but should be in tool descriptions.