Cobro-mcp defines 6 tools with clear, domain-specific names (open, wait, status, done, screenshot, close) that follow verb_noun conventions. All tools have descriptions (avg ~150 chars, within baseline 194). Input schemas are present and use Zod validation with type constraints. However, parameter descriptions are sparse or missing in several tools, output schemas are not documented, and error handling lacks recovery guidance. The server targets a specialized co-browsing workflow, which constrains generality but improves focus.

• Document output schemas for all tools. E.g., open() returns {title: string, restarted: boolean}; wait() returns {status: 'pending'|'ready', payload?: {batches: Array<{note: string, ...}>}, browserGone?: boolean}. Include field descriptions and types.
• Expand parameter descriptions to 50-150 chars with constraints. E.g., 'timeoutSec: Wait duration in seconds (5-7200, default from server config). Use 50 for Cursor/Codex, 1800 for Claude Code.' Add enum/range constraints to schema.
• Add error handling guidance. Document: (1) what errors each tool can raise (e.g., 'browserGone', 'timeout', 'auth failed'), (2) whether they're retryable, (3) recovery steps. E.g., 'If browserGone, call open() again to restart.'
• Clarify wait() retry semantics. Document: max retries, recommended backoff (e.g., 100ms), and when to give up. Add a 'maxRetries' parameter or guidance in description.
• Enhance close() description to explicitly state it's destructive and irreversible. Add risk annotation (destructiveHint: true) to signal to agents this is a terminal operation.