Two tools with minimal documentation. list_passwords has a basic description (READ-ONLY access) but no visible input schema. get_password has a description and visible input schema with two optional parameters (domain, name), but both lack detailed descriptions explaining format/constraints. No output schemas documented. No error handling guidance. No parameter validation rules stated. Descriptions are under 100 chars, below the 194-char baseline for production tools. Tool composition is reasonable (two distinct read-only operations), but schema completeness and parameter documentation are weak.

• Add explicit input schema to list_passwords with pagination parameters (limit, offset) and return type (array of password entries with metadata fields).
• Expand get_password parameter descriptions: 'domain (string, required if name omitted): FQDN or service name to look up, e.g. "api.example.com". name (string, optional): human-readable entry name if domain lookup fails. Exactly one of domain or name must be provided.'
• Document output schema for both tools. For get_password, specify: returns {alias: string, proxyUrl: string, upstreamUrl: string} or error object with code and message.
• Add error handling guidance: 'If domain not found, returns error code NOT_FOUND with available domains. If vault locked, returns VAULT_LOCKED, ensure vault is initialized before calling.'
• Expand tool descriptions to 150 - 250 chars explaining purpose, when to call, and what to expect. E.g. 'List all password entries with metadata (READ-ONLY). Call this first to discover available credentials. Returns array of {name, domain, createdAt}. Does not expose actual passwords.'