Single tool (search_web_tool) with complete input schema and reasonable description. Naming follows verb_noun pattern (search_web). Schema includes proper types, descriptions, and constraints (count 1-20, defaults). However, output schema is not formally documented, only inferred from code comments. Error handling is present but generic (ValueError, Exception). No tool annotations (readOnlyHint, destructiveHint). Description is 94 chars, adequate but could be more prescriptive about when to use vs alternatives. Parameters are well-described with ranges and nullable flags. Risk classification (READ_ONLY) is correct but not exposed in schema metadata.

• Move api_key to server-side environment variable injection. Remove from tool parameters. Update tool to read from os.environ['BRAVE_API_KEY'] or similar.
• Document output schema explicitly in tool docstring: 'Returns: List[Dict] with fields: title (str), url (str), description (str), score (float 0.0-1.0)'.
• Add tool annotations to schema: readOnlyHint=true (search is safe), idempotentHint=true (same query always returns same results).
• Enhance error messages with recovery guidance: 'Rate limit exceeded. Retry after 60 seconds or check https://brave.com/account/usage for quota.' instead of bare 'Rate limit exceeded'.
• Add total_count and next_cursor to response. Return {results: [...], total_count: 42, next_cursor: 'offset_20'} to enable safe pagination.