Personae MCP provides 20 tools for browser automation across multiple identities. Tool naming follows verb_noun convention (list_identities, open_identity, navigate, etc.), which is good. However, descriptions are inconsistent in depth and quality. Most descriptions are 50-150 chars, which is acceptable, but lack actionable context about when to use each tool vs. alternatives. Parameter schemas are present but minimal, most parameters have only type and description, with no enums, ranges, or validation constraints. Output schemas are not documented anywhere in the visible code. Error handling is absent from descriptions. The server lacks guidance on tool composition (e.g., 'call snapshot() before click()' is mentioned in click's description but not consistently applied). No security considerations are documented despite tools performing write operations on browser state.

• Document output schemas for all tools. For list_identities, specify: returns {identities: [{id: string, name: string, partition: string, isOpen: boolean, targetId: string, childWindows: string[]}], total: number}. For snapshot, specify: returns {dom: string, elements: {[key: string]: {selector: string, text: string, type: string}}}.
• Replace overloaded 'identity' parameter with separate identity_id, identity_name, and identity_partition parameters, or add an enum constraint and validation logic that accepts all three formats but documents the precedence (e.g., 'id takes precedence if provided').
• Add error recovery guidance to every tool description. E.g., navigate: 'Returns error if identity not found (call list_identities to verify) or URL is invalid (check format).' click: 'Returns error if selector not found (call snapshot() first to establish references, or use CSS selector instead of @e reference).'
• Document tool dependencies explicitly. Add to snapshot description: 'Call this before click, hover, focus, select, check, uncheck to establish element references.' Add to click description: 'Requires prior snapshot() call in same session to resolve @e references.'
• Add parameter constraints: scroll x/y should be bounded (e.g., -5000 to 5000 pixels); load_skill should have enum of valid skill names (e.g., 'core', 'advanced'); press should document valid key names (e.g., 'Enter', 'Escape', 'Tab', 'ArrowUp', 'ArrowDown').