Two tools with minimal definitions. Both lack input schemas (empty {} objects), descriptions are present but generic (50-60 chars), and no parameter documentation exists. Tool names follow verb_noun pattern (get_, list_) but schemas are completely absent. No output schema documentation visible. Error handling not evident. This server fails basic definition quality standards.

• Add explicit input schemas to both tools. Even if no parameters are needed, declare Input: {type: 'object', properties: {}, required: []} to signal intentional emptiness. Better: add optional parameters like 'include_metadata' (boolean) or 'format' (enum: json|csv) to increase utility.
• Expand descriptions to 150-250 chars. Example: 'get_chef_iq_status: Retrieve the current connection status and setup state of the CHEF iQ device. Returns whether the device is connected, paired, and ready to report temperatures. Call this first to verify device availability before reading probe data.'
• Document output schemas in descriptions or as separate schema blocks. Example: 'Returns: {connected: boolean, setup_complete: boolean, last_sync: ISO8601 timestamp, error?: string}'.
• Add pagination to list_chef_iq_probes. Include optional 'limit' (1-100, default 20) and 'offset' (default 0) parameters. Return total_count and next_offset in response to enable iteration over large probe lists.
• Add error handling guidance. Describe what happens if the device is offline, not paired, or returns stale data. Example: 'If connected=false, the device is unreachable. Check network connectivity and restart the device.'