Three tools with complete schemas and descriptions, but significant gaps in parameter documentation and error guidance. Tool names follow verb_noun convention (activity_recent, activity_search, activity_digest). Descriptions are present (avg 180 chars) and explain WHEN to use each tool, which is good. However, most parameters lack descriptions entirely, 'scope', 'agent', 'host', 'group_by' have no guidance on valid values or constraints. Output schemas are not documented. Error handling is minimal: the code catches timeouts and exit codes but provides no recovery guidance to the LLM. No parameter validation rules stated (e.g., what values does 'group_by' accept? What format is 'since'?). The 'since' parameter in activity_search accepts '7d' and 'since:<ULID>' but this is only documented in the description, not as an enum or pattern constraint.

• Add descriptions to all parameters. For 'group_by', document: 'Group results by scope, agent, or kind. Determines how the digest is organized.' For 'scope', 'agent', 'host': explain what these filter on and provide examples of valid values.
• Document output schemas for each tool. Specify what fields are returned (e.g., activity_recent returns [{id, timestamp, scope, agent, summary, ...}]) so LLMs know what to extract.
• Add error recovery guidance. When the daemon is not found or times out, return: 'The activity-mesh daemon may not be running. Ensure it is started with: activity-mesh-daemon' or similar.
• Constrain 'since' parameter in activity_search with an enum or pattern. Replace prose description with: enum: ['1d', '7d', '30d'] or pattern: '^(\d+[dhm]|since:[A-Z0-9]{26})$'.
• Document result limits and pagination. Add to activity_search description: 'Returns up to 20 most recent matches. To fetch more, adjust the limit parameter (max 100) or narrow the time window with since/until.'