Two tools with complete input schemas and descriptions, but descriptions are generic and lack LLM-optimized guidance. Parameter descriptions are present but minimal (10-30 chars). No output schema documentation. Error handling exists but lacks recovery guidance. Naming is clear (verb_noun pattern). No tool annotations or composition patterns evident.

• Document output schemas for both tools. E.g., search_death_notices returns {count, page, nextPage, records: [{id, firstname, surname, dateOfDeath, locations, url}]}. get_death_notice returns {name, dateOfDeath, location, description, funeralDetails, charityInfo}.
• Expand parameter descriptions to 50-100 chars with format and semantic clarity. E.g., date_from: 'Earliest creation date (YYYY-MM-DD HH:MM:SS). Inclusive. Filters by when the notice was published, not death date.'
• Add county as an enum parameter with all 32 valid values (Antrim, Armagh, ..., Wicklow) instead of free-form string validation.
• Enhance tool descriptions with WHEN/WHY. E.g., 'Use search_death_notices to find multiple notices by name/location/date. Use get_death_notice to fetch full details (description, funeral arrangements, charity) for a specific notice ID from search results.'
• Add error recovery guidance. E.g., 'If county is invalid, return: "Unknown county. Valid options: Antrim, Armagh, ..." If API times out, retry with smaller date range or fewer filters.'