InitRunner provides 11 tools with clear verb-noun naming and consistent parameter structures. However, quality is uneven: tool descriptions are brief (mostly 10-50 chars) and lack LLM-optimized context about WHEN to use each tool. Parameter descriptions exist but are minimal. Output schemas are not documented, we can infer some structure (e.g., search_inbox likely returns email metadata, read_email returns content) but cannot verify from source. Error handling and recovery guidance are absent. The tools themselves are well-scoped (one action each), but descriptions fall short of production standards (baseline 194 chars average; these average ~65 chars). Tool composition is reasonable, related tools (search_inbox, read_email, list_folders) work together, but descriptions don't guide the LLM on sequencing or dependencies.

• Expand tool descriptions to 100-200 characters. For each tool, add: (1) what it does, (2) when to use it vs. similar tools, (3) key prerequisites or constraints. Example: 'Search for emails in your mailbox using IMAP syntax. Use this to find specific messages by sender, subject, or date. Returns up to limit results; use page/offset for pagination. Requires IMAP access to be configured.'
• Document output schemas explicitly. For search_inbox, specify: 'Returns {messages: [{message_id: string, subject: string, from: string, date: ISO8601, preview: string}], total_count: int, has_more: bool}'. For read_email: 'Returns {message_id: string, subject: string, from: string, to: string[], cc: string[], date: ISO8601, body: string, attachments: [{name: string, size: int}]}'.
• Add error handling and recovery guidance. For parse_date, add: 'If format is invalid, returns error with hint. Example: Invalid format '%Y-%m-%d', try ISO 8601 format (YYYY-MM-DD) instead.' For search_inbox: 'If IMAP query is malformed, returns error with suggestion. If folder does not exist, returns 'Folder not found. Call list_folders() to see available options.'
• Clarify search_inbox pagination: document exact behavior for limit=0, maximum limit value, and whether it returns cursor/total_count/has_more for chaining.
• Add constraint documentation for convert_units: explicitly list supported unit pairs (km↔mi, kg↔lb, c↔f, l↔gal, m↔ft, cm↔in) as an enum or pattern in the schema, not just in the description. Prevent LLMs from hallucinating 'kg↔gal' conversions.