Agentenna exposes 4 read-only tools with clear verb-noun naming (list, listen, rewind, inspect). All tools have descriptions and input schemas with typed parameters. However, parameter descriptions are sparse or missing for optional fields, output schemas are not documented, and error handling guidance is absent. The tools are well-composed for a single domain (channel awareness), but lack the depth of documentation and error recovery patterns expected in production tools.

• Document output schemas for all tools. For agentenna_listen and agentenna_rewind, describe the XML structure (e.g. root element, child tags, attributes). For agentenna_list_channels, document the dict fields (e.g. channel_name, event_count, etc.). For agentenna_inspect, document the event payload structure.
• Add descriptions to all optional parameters in agentenna_rewind. E.g. 'query: Free-text search across event messages and metadata. Omit to return all events in the window.' 'severity_min: Filter to events at or above this level (crit, high, med, low). Omit for all severities.'
• Add error handling guidance. E.g. 'If channel not found, returns empty list. Call agentenna_list_channels to see available channels.' 'If event_id does not exist, returns 404 with available event IDs in the time window.'
• Document parameter constraints. E.g. 'window: Duration string (e.g. 30m, 1h, 7d). Default 30m. Max 365d.' 'limit: Integer 1 - 1000. Default 20. Results beyond limit are truncated; use pagination cursor (if supported) for more.'
• Add tool annotations (readOnlyHint) to signal to clients that all tools are safe to call without user confirmation. This improves agent autonomy for read-only operations.