Two tools with minimal descriptions (both under 50 chars) and basic schemas. 'search' lacks parameter descriptions; 'createSummary' has only videoId with minimal context. No output schemas documented. No error handling guidance. No parameter constraints (enums, ranges). Naming is verb-based but descriptions fail to explain WHEN to use each tool or WHAT they return. Missing dependency hints (e.g., 'search first to get videoId'). No indication of API rate limits, timeout behavior, or failure modes.

• Expand tool descriptions to 100-200 chars. For search: 'Search YouTube for videos matching a query. Returns up to 20 results with videoId, title, and channel. Use this first to find videos before summarizing.' For createSummary: 'Generate a text summary from a YouTube video transcript. Requires a valid videoId from search results. Returns a concise summary (200-500 words) of the video content.'
• Add parameter descriptions: query → 'Search terms (e.g., "machine learning tutorial"). Supports YouTube search operators.'; videoId → 'YouTube video ID (11-char alphanumeric, e.g., from search results). Must be a valid, public video with available transcript.'
• Document output schemas in tool descriptions or as JSON examples. E.g., search returns [{videoId, title, channelTitle, publishedAt}]; createSummary returns {summary, wordCount, duration}.
• Add error handling guidance: 'If videoId is invalid, search for the video first. If transcript unavailable, the video may be private or lack captions. If rate limited, wait 60 seconds before retrying.'
• Add pagination to search: include limit (default 20, max 50) and nextPageToken parameters. Document that results are capped at 50 to prevent context explosion.