Three read-only tools with basic descriptions but significant gaps in schema documentation and parameter clarity. Tool names lack action verbs (context_usage, rate_limits, session_summary are nouns). Input schemas visible but minimal, session_id parameters lack type constraints and validation guidance. Descriptions are adequate (100-150 chars) but do not explain when to use each tool vs. alternatives or what downstream operations they enable. No output schemas documented. Error handling absent.

• Rename tools with action verbs: 'context_usage' → 'get_context_usage', 'rate_limits' → 'get_rate_limits', 'session_summary' → 'get_session_summary'. This matches the 90% baseline of A+ tools starting with action verbs.
• Document output schemas for each tool. Specify field names, types (string, number, object, array), and nesting. Example: context_usage returns {session_id: string, used_tokens: number, max_tokens: number, percent_of_window: number, percent_of_usable: number}.
• Add validation guidance to session_id parameter: 'Optional UUID string (36 chars, e.g. d6486277-...). If omitted, the most-recently-updated session is used.' Include format constraint in schema.
• Document error cases and recovery paths. E.g., 'If session_id is invalid, returns error with available session IDs. If state file is missing, returns error suggesting to run Claude Code first.'
• Add tool selection guidance in descriptions. E.g., context_usage: 'Use to monitor token consumption for a specific session. For a quick snapshot of both context and rate limits, use session_summary instead.'