LeftGlove provides 7 browser automation tools with basic descriptions but critical gaps in schema documentation and parameter clarity. Tool names are action-oriented (observe, click, fill, navigate, screenshot, element-screenshots, status) but parameter schemas are incomplete or inferred from scattered source files. Most tools lack formal input schema definitions visible in the code. Descriptions are present but generic (10-80 chars), below the 50-200 char baseline for LLM optimization. No output schemas documented. Error handling and recovery guidance absent. The observe tool is well-named but lacks schema detail; click/fill accept multiple input modes (index, coordinates, selector) without clear mutual exclusivity documentation. No tool declares permissions, audit trails, or idempotency guarantees.

• Add formal JSON Schema input definitions for all tools. For click/fill, use oneOf to enforce mutual exclusivity: {oneOf: [{required: ['index']}, {required: ['x', 'y']}, {required: ['selector']}]}. Make schema visible in tool registration.
• Document output schemas for all tools. E.g., observe returns {elements: [{index: number, selector: string, text: string, locator: string}], total: number}. Include in tool description or separate schema field.
• Expand descriptions to 80-150 characters. Example: 'Inject sieve.js into the page and return a structured inventory of interactive elements with stable CSS selectors and coordinates. Use this first to discover elements before clicking or filling.'
• Add error handling guidance to click, fill, navigate. E.g., 'If element not found, call observe() to refresh the inventory and verify the index. If URL is invalid, check the protocol (http/https) and domain.'
• Declare tool permissions and idempotency. E.g., click/fill/navigate are destructive (write); observe/screenshot/status are read-only. Mark screenshot and observe as idempotent (safe to retry).