Two tools with basic schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. readDocumentation has a minimal 1-param schema; searchDocumentation has 3 params with enums and defaults. Both descriptions are under 100 chars and lack context on when to use each tool or what they return. No error handling guidance, no output schema documentation, and parameter descriptions are sparse. Tool names follow verb_noun convention (positive), but lack the specificity needed for LLM disambiguation (e.g., 'readDocumentation' vs 'searchDocumentation' could be clearer about scope: LINE Developers site only).

• Document output schemas for both tools. Add to tool descriptions: 'Returns: {content: [{type: "text", text: string}]}' for readDocumentation and 'Returns: [{url, title, description, type}]' for searchDocumentation.
• Expand parameter descriptions with constraints and examples. E.g., 'url: Full URL to LINE Developers documentation page (https://developers.line.biz/...). Must be a valid documentation URL.' and 'searchPhrase: Search keywords (1-200 chars, supports English and Japanese).'
• Add context to tool descriptions explaining when to use each. E.g., 'Use searchDocumentation to find relevant docs by keyword, then readDocumentation to fetch full content.'
• Include error recovery hints in tool descriptions. E.g., 'If URL is invalid, returns empty content. Verify URL is from developers.line.biz.'
• Document pagination behavior for searchDocumentation: 'Returns up to 20 results per page. Use pageNumber to iterate. Returns empty array if no results match.'