Two well-defined read-only tools with complete input schemas, clear descriptions, and proper output schema documentation. Tool names follow verb_noun convention (search_, get_). Descriptions are concise (60 - 90 chars) and explain purpose clearly. Input parameters have types, descriptions, and constraints (min/max, enums, defaults). Output schemas are formally defined with Zod. Annotations correctly mark both tools as read-only and idempotent. Minor gaps: parameter descriptions could be more prescriptive about format/range; no error recovery guidance in descriptions.

• Enhance parameter descriptions with format constraints: 'query: Search query (1 - 2048 characters, case-insensitive, supports partial words)' instead of just '(1 - 2048 characters)'.
• Add recovery guidance to tool descriptions: 'If no results found, try a shorter or more general query. If offset exceeds totalCharacters, use nextOffset to fetch remaining text.'
• Document output schema fields in descriptions: 'Returns omittedForBudget (count of results excluded due to token limits) and nextOffset (character position for pagination, or null if end reached)'.
• Consider adding a 'batch_get_audit_references' tool to fetch multiple findings in one call, reducing round-trips for common multi-finding workflows.
• Add explicit error examples to descriptions: 'Returns error if finding ID does not exist; try search_audit_references to discover valid IDs.'