Single tool with minimal definition quality. Tool name 'getSshCredentialByIp' uses camelCase (Java convention) rather than snake_case verb_noun pattern expected by LLMs. Description is only 23 characters ('Get SSH credential by IP'), below the 50-200 char baseline for LLM-optimized descriptions. Input schema present but parameter description is minimal (7 chars: 'IPv4 address'). No output schema documented. No error handling guidance. Tool returns hardcoded credentials, raising security concerns. Overall definition lacks the depth needed for reliable agent selection and execution.

• Rename tool to 'get_ssh_credential_by_ip' (snake_case verb_noun) to align with LLM tool discovery patterns and the 549-tool baseline where 90% of A+ tools start with action verbs.
• Expand tool description to 80-150 characters explaining: what it does, when to call it (e.g., 'before establishing SSH connections'), what it returns (IP, username, password, port), and any prerequisites (e.g., 'IP must be registered in the credential store').
• Document the output schema explicitly: 'Returns SshCredential object with fields: ip (string), user (string), password (string), port (string)'. This enables agents to plan downstream tool calls.
• Add parameter constraints to description: 'IPv4 address in dotted-decimal notation (e.g., 192.168.1.1). Must be a registered host in the credential store. Returns 404 if not found.'
• Replace hardcoded credentials with actual secret injection: fetch credentials from a vault (HashiCorp Vault, AWS Secrets Manager) or environment variables. Never return plaintext passwords in tool responses; use a reference or token instead.