DataPulseSSE has 2 tools with minimal definition quality. Tool names are acceptable (get_time, fetch_url) and start with verbs, but descriptions are extremely sparse (13-26 characters, well below the 10-1024 character recommendation). Most critically, the fetch_url tool's schema is severely incomplete: it declares a 'url' parameter with a type and basic description, but get_time declares an empty input schema {}. Parameter descriptions are present but superficial. No output schemas are documented anywhere in the code, LLMs cannot determine what fields to expect from responses. Error handling is minimal: catch-all exception blocks return generic error strings without guidance on recovery or error classification. No input validation is shown, and the fetch_url tool accepts arbitrary URLs with a 5-second timeout, creating potential security and reliability issues. The tools lack any indication of idempotency, read-only status, or destructive intent in their descriptions.

• Document output schemas for both tools. Example for get_time: 'Returns {"time": "<ISO 8601 UTC string>"} with the current server time in UTC.' For fetch_url: 'Returns {"status": <HTTP status code int>, "content": "<first 200 characters of response body as string>"}'
• Expand tool descriptions to 50-150 characters with WHAT, WHEN, and implications. E.g., get_time → 'Get the current server time in UTC ISO 8601 format. Use this to timestamp operations or check if the server is responsive. Returns a single time value.' fetch_url → 'Retrieve and return the HTTP response from a provided URL. Returns only the first 200 characters of the response body. Use to preview web content, check endpoint availability, or fetch small config files. Requests timeout after 5 seconds.'
• Add explicit enum constraints or format patterns to the url parameter. E.g., add to parameter description: 'Must be a valid HTTP or HTTPS URL (e.g., https://example.com/path). No localhost, file://, or data: schemes allowed.'
• Implement input validation with actionable errors. For fetch_url: validate URL format before calling requests.get(). Return '{"error": "Invalid URL format. Expected http:// or https:// scheme. Got: \"<url>\""}' instead of a generic exception.
• Add error classification and recovery guidance. Wrap requests.get() with specific exception handling: on requests.Timeout → return '{"error": "Request timeout after 5 seconds. URL may be slow or unreachable. Try a different endpoint."}'; on requests.RequestException → return '{"error": "Failed to fetch URL: <reason>. Check the URL is valid and accessible."}'; on other exceptions → return '{"error": "Unexpected error: <details>. This is a server error; retry after a moment."}'