BrowserBro exposes 2 tools (browserbro_googlesearch, browserbro_screenshot) via the MCP SDK. Both tools are registered with input schemas derived from plugin implementations, but the actual schema definitions and parameter descriptions are not visible in the provided source code. The code shows that tools are registered dynamically from plugins (pkg/mcp/tools.go, line ~20: `schema := plugin.InputSchema()`), but the plugin implementations (pkg/plugins/googlesearch/googlesearch.go and pkg/plugins/screenshot/screenshot.go) are not included in the source excerpt. This means schema quality, parameter naming, and descriptions cannot be verified from the provided code. The tool registration mechanism is sound (panic recovery, nil-schema checks), but without visibility into the actual plugin schema definitions, we must score conservatively. The names follow a reasonable verb_noun pattern (googlesearch, screenshot) but lack clear action verbs (search_web, take_screenshot would be stronger). No tool descriptions are visible in the registration code provided.

• Provide the actual plugin implementation files (pkg/plugins/googlesearch/googlesearch.go and pkg/plugins/screenshot/screenshot.go) to verify InputSchema() returns valid JSON Schema with property descriptions and type constraints.
• Rename tools with clear action verbs: 'browserbro_googlesearch' → 'search_web_google' or 'search_google', 'browserbro_screenshot' → 'take_screenshot'. This helps LLMs infer intent from the name alone.
• Ensure each plugin's Description() method returns a 50 - 200 character description answering: What does this tool do? When should it be called? Example: 'Takes a screenshot of a URL and saves it as an image file. Use this to capture web pages for visual inspection.'
• Document output schemas explicitly in plugin descriptions or via a separate schema method. Specify the fields returned (e.g., for screenshot: {file_path, width, height, format}) and their types.
• Verify all input schema properties include 'description' fields. For googlesearch, document what 'query' means, character limits, supported operators, etc. For screenshot, document URL format, timeout, viewport size options.
• Add error recovery guidance in descriptions. Example: 'If the URL times out, try a simpler page or check the URL is accessible.' This helps LLMs self-correct.
• Consider implementing idempotentHint and readOnlyHint annotations in the Tool struct (if using MCP SDK ≥2026-07-28) to signal that both tools are read-only and safe to retry.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry