Single tool with critical definition gaps. Tool name 'query_aws_docs' lacks action clarity (query vs search ambiguity). Description is present but generic (72 chars, below 100-char minimum for clarity). Input schema visible but parameters lack descriptions entirely, 'query' and 'service' have no guidance on format, constraints, or when to use each. No output schema documented. No error handling guidance. No pagination despite AWS docs being large. Violates 8+ core patterns from the rubric.

• Rename tool to 'search_aws_docs' and update description to: 'Search AWS official documentation for information about services, APIs, and features. Returns the top result with title, excerpt, and source URL. Use the optional service parameter to filter by service name (e.g., ec2, s3, lambda).'
• Add parameter descriptions: query='Search terms (e.g., "S3 bucket policies", "Lambda concurrency limits"). Required.'; service='AWS service name to filter results (e.g., ec2, s3, lambda, rds). Optional. If omitted, searches all services.'
• Document output schema in tool definition: {response: string (excerpt from documentation, max 1000 chars), source_url: string (full URL to AWS docs page)}
• Add pagination: accept 'limit' (1-20, default 10) and 'offset' (default 0) parameters. Return {results: [{title, excerpt, url}], total_count: int, has_more: bool}
• Improve error handling: catch specific exceptions (httpx.TimeoutException, httpx.ConnectError, BeautifulSoup parse errors) and return structured errors: {error: 'service_unavailable', message: 'AWS docs search timed out. Try again in 30 seconds or use a more specific service filter.', retryable: true}