The tool lacks parameter descriptions, output schema documentation, and error handling guidance. No tool annotations present. The server implements a custom WebSocket protocol rather than MCP, making tool definitions non-standard and unverifiable against MCP patterns.

• Migrate from custom WebSocket to MCP protocol. Implement stdio or HTTP transport with proper MCP message framing (initialize, call_tool, etc.).
• Define explicit input schema for checkPjsipEndpoints. Even if no parameters are required, document the empty schema with 'type: object, properties: {}, required: []' and explain what the tool does without parameters.
• Document output schema. Specify the structure of the response (e.g., array of endpoint objects with fields: name, status, registration_status, etc.).
• Add error handling guidance. Include recovery hints: 'If Asterisk is unreachable, verify connection config and retry. If no endpoints found, check Asterisk configuration.'
• Add tool annotations. Mark checkPjsipEndpoints with readOnlyHint: true since it only retrieves data without modification.