Mantis provides 11 tools with complete input schemas and descriptions. Naming follows verb_noun convention (list_, inspect_, find_, trace_, explain_, get_, select_, filter_, set_, frame_). Descriptions are concise (40-120 chars) and action-oriented. However, parameter descriptions are minimal or absent in several tools (filter_events, set_source_filter, frame_trace lack detail on valid values). Output schemas are not documented. Error handling guidance is absent. Tool composition is reasonable but some tools conflate UI state manipulation with data inspection (select_event, filter_events, set_source_filter are UI-only writes without clear recovery paths). No pagination, no batch operations, no idempotency guarantees documented.

• Add enum constraints to all free-form string parameters. Replace 'type' description with: 'Event kind to filter by. Must be one of: user, webmcp, network, state, render, console.'
• Document output schemas for all tools. Example: 'list_sessions returns {sessions: [{id: string, status: string, errorCount: number}], total: number}'.
• Add recovery hints to parameter descriptions. Example for sessionId: 'Session ID returned by list_sessions. Call list_sessions first if you don't have a valid ID.'
• Separate UI manipulation tools from data inspection. Consider wrapping select_event, filter_events, set_source_filter, frame_trace into a single 'update_ui_state' tool with a structured payload, or document idempotency guarantees.
• Add error classification to tool descriptions. Example: 'Returns 404 if sessionId not found (retryable after calling list_sessions). Returns 400 if sessionId format is invalid (user-fixable).'
• Document pagination and result limits. If list_sessions or find_errors can return large result sets, add limit and offset/cursor parameters.