11 tools with schemas present but significant quality gaps. Tool names follow verb_noun pattern (apollo_*, cdp_*) but descriptions are minimal (10-30 chars, well below 50-200 char baseline for A+ tools). Parameters lack descriptions in most cases, only 'sessionId' and primary params have brief text. No output schemas documented. Error handling absent. Apollo tools expose GraphQL internals without guidance on when to use each variant. CDP tools lack safety warnings for destructive operations (clear_cookies, reload). No idempotency hints or recovery guidance.

• Expand all tool descriptions to 80-150 chars. Example: 'apollo_inspect_cache' → 'Inspect Apollo Client cache state for a GraphQL query. Use this to debug cache misses or verify cached data before refetching. Returns cache entry or null if not found.'
• Document output schemas for all tools. Example: apollo_inspect_cache returns {cacheEntry: object | null, query: string, variables: object}. cdp_screenshot returns {dataUrl: string, width: number, height: number}.
• Add parameter descriptions for all optional params. Example: sessionId → 'Chrome DevTools Protocol session ID. If omitted, uses the default/active session. Obtain via cdp_list_sessions or browser automation setup.'
• Implement confirmation pattern for destructive tools. apollo_clear_cache and cdp_clear_cookies should accept a 'confirm: true' parameter and return {status: 'pending_confirmation', message: 'This will clear all cached data. Pass confirm=true to proceed.'}
• Add error recovery guidance. When a tool fails, return {error: 'message', retryable: boolean, nextSteps: ['Try X', 'Or call Y tool']}. Example: 'sessionId not found. Retryable: true. Next steps: ["Verify Chrome is running", "Call cdp_list_sessions to find active session"]'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry