Single tool with critical gaps. Tool name 'get_1password_credentials' follows verb_noun pattern (positive), but description is only 47 chars, below the 10-1024 baseline and lacks WHEN/WHY context. Input schema present but parameter 'item_name' has no description (violates pattern:tool-description). No output schema documented, LLM cannot plan downstream use. No error handling guidance. Credentials returned in response violate pattern:secret-injection (secrets should never appear in tool output). No pagination, no validation, no recovery guidance.

• Redesign to return only a reference/token, not plaintext credentials. E.g., return {credential_id: 'cred_xyz', expires_at: '2025-01-15T10:00:00Z'} and let downstream tools request decryption via a separate secure channel.
• Add parameter description: 'item_name (string, required): The name of the 1Password item to retrieve. Must match exactly (case-sensitive). Examples: Gmail, AWS, GitHub.'
• Expand tool description to 120+ chars: 'Retrieve stored credentials from 1Password for a given item name. Returns email and password. Requires OP_SERVICE_ACCOUNT_TOKEN env var. Use this to fetch login credentials for automated tasks.'
• Add explicit error handling: catch 'item not found' and return {error: 'Item not found', suggestion: 'Call list_1password_items() to see available items'} instead of raw exception.
• Document output schema in description or as a separate schema block: 'Returns {email: string, password: string}' or consider returning {credential_reference: string, expires_at: string} to avoid exposing secrets.