🔍 THE PRIMARY SENTRY SEARCH TOOL - Use this when the user asks to: 'check sentry', 'look at errors', 'search sentry', 'what's breaking', 'show me errors', 'find this exception', 'any new crashes', 'unresolved issues', 'top errors', 'how many errors', 'error rate', or 'error trend'. Searches grouped issues across the whole org automatically (no project needed) or filtered by a specific project. Uses Sentry search syntax in query (e.g. 'is:unresolved level:error', 'is:unresolved release:latest', free text like a message or exception type). Set count=true to get error event COUNTS and a TREND chart over time instead of the issue list.

🔗 TRACE ID LOOKUP TOOL - Use when the user mentions a Sentry trace ID (a 32-char hex string like 'ce8f0d3961214198a040517b3dfda0d4') or asks: 'find this trace', 'what happened in this request', 'follow this trace across services', 'what services touched this request', 'show the trace timeline', or 'distributed trace'. CRITICAL: when a user pastes a trace ID and asks to find/follow it, use THIS tool - not search_issues. It returns every span and error across all projects/services that participated in the trace, grouped by service with a timeline.

🔎 ROOT CAUSE TOOL - Use when the user asks: 'what happened before this error', 'show the stack trace', 'get context', 'why did this fail', 'details of this issue', 'what led to this', or as a follow-up after finding an interesting issue with sentry_search_issues. Fetches the full picture of one issue: summary (level, counts, first/last seen), the exception + stack trace, the BREADCRUMBS (the chronological events leading UP TO the error - the equivalent of 'logs before'), request context, tags, and the trace ID for cross-service investigation.

🧩 Use when the user asks: 'group similar errors', 'what error patterns', 'types of errors', 'categorize errors', 'what's the breakdown', 'do we have one problem or many', or during an incident. Sentry already groups events into issues; this tool ranks those issue groups by event volume and merges near-duplicate issue titles (stripping IDs/UUIDs/numbers) into higher-level patterns. ESSENTIAL for incident triage - instantly see whether you have 1 dominant problem or 50 different ones, and which patterns drive the most events.