8 tools with basic descriptions and partial schemas. Most tools have input schemas with type definitions, but descriptions are inconsistent in depth. browse_page has a detailed description (194 chars) exceeding baseline; others are terse (20-80 chars). No output schemas documented. Error handling absent, tools do not guide recovery or categorize failures. Parameter descriptions exist but lack constraints (enums, ranges, format specs). No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Naming is verb-forward (browse_, click_, extract_, fill_, press_, close_, list_) but some names are generic (extract_text, press_key). No documented composition or chaining guidance.

• Document output schemas for all tools. browse_page should return {title: string, url: string, status: number, text: string}. screenshot should return {base64: string, width: number, height: number}. list_browsers should return {browsers: [{name, path, profiles}]}.
• Add error handling guidance to each tool description. E.g. 'If selector not found, returns error 404 with available selectors. Retry with corrected selector or call extract_text to inspect page structure.'
• Convert parameter examples to enums or format specs. press_key: enum=[Enter, Escape, ArrowDown, ArrowUp, Tab, Backspace, Delete, Home, End]. selector: description='CSS selector (e.g. #id, .class, button[type=submit])'.
• Add tool annotations: browse_page and extract_text and screenshot and list_browsers get readOnlyHint=true. click_element, fill_input, press_key get destructiveHint=true. close_browser gets destructiveHint=true.
• Expand descriptions to 80-150 chars with context. E.g. click_element: 'Click an element by CSS selector to trigger interactions (buttons, links, checkboxes). Use after extract_text to locate the selector. Returns success or error with available selectors if not found.'