8 tools with basic schemas and minimal descriptions. All tools have input schemas with required fields properly declared, but descriptions are generic (10-50 chars) and lack context for LLM selection. No parameter descriptions beyond selector/value/script. No output schemas documented. No error handling guidance. Tool names follow verb_noun pattern (navigate, evaluate, click) but lack specificity about what state changes occur. Missing idempotency, retry guidance, and recovery instructions.

• Add output schemas to all tools. E.g., yunbrowser_screenshot should document: {type: 'object', properties: {image_data: {type: 'string', description: 'Base64-encoded PNG'}, url: {type: 'string'}}}
• Expand tool descriptions to 100-200 chars. Example: 'Navigate to a URL and wait for page load. Returns the final URL after redirects. Use before calling other page interaction tools. Fails if URL is invalid or unreachable.'
• Add descriptions to all parameters. E.g., selector: 'CSS selector string (e.g., #button-id, .class-name, div > p). Required. Returns error if no matching element found.'
• Document error responses with recovery guidance. E.g., 'If selector not found, call yunbrowser_get_text() to inspect page content, then retry with corrected selector.'
• Add idempotentHint and destructiveHint annotations to tool definitions. Mark yunbrowser_evaluate as destructive (arbitrary JS execution). Mark yunbrowser_navigate as idempotent (same URL = same state).