Brijio MCP server has 16 tools with complete input schemas and descriptions. Naming follows verb_noun convention (perform_batch, capture_screenshot, click_element). Descriptions are present but brief (avg ~80 chars, below the 194-char baseline). Parameters are typed and mostly described, but lack depth on constraints, formats, and dependencies. Output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages visible. Tools are well-composed (single responsibility) and support browser automation workflows. Missing: pagination guidance, output schema documentation, and detailed parameter constraints.

• Document output schemas for all 16 tools. Specify field names, types, and whether results are paginated. E.g., list_browsers should return {browsers: [{id: string, name: string, ...}], total: number}.
• Expand tool descriptions to 100-200 chars. Add WHEN to use (e.g., 'Use perform_batch to execute multiple form actions in one call, reducing round-trips'), prerequisites, and dependencies on other tools.
• Add explicit parameter constraints: perform_batch actions array must contain objects with 'type' enum (click|write_text|set_checked|select_options|submit_form|upload_file) and required fields per type.
• Document error scenarios and recovery paths. E.g., 'If click_element fails with "element not found", call capture_screenshot to verify page state, then retry with correct element ID.'
• Add per-tool error handling guidance: which errors are retryable (network timeout), which require user input (element not found), and which are fatal (invalid browser instance).