Three tools with basic schemas and descriptions, but significant gaps in parameter documentation, output schema clarity, and error handling guidance. All tools have names starting with action verbs (query-, insert-, update-) and descriptions present, but descriptions are generic (avg 95 chars, below 194-char baseline). Parameters lack detailed constraints, format specifications, and dependency documentation. No output schemas documented. Error handling is minimal, tools throw generic errors without recovery guidance. StorageService.queryRecords() has SQL injection vulnerability (string interpolation in query). No pagination support despite potential for large result sets.

• Replace string interpolation in queryRecords() with parameterized queries: use Cosmos SDK's query builder or prepared statements to prevent SQL injection.
• Document output schemas for all tools. E.g., query-records returns {records: [{id, partitionKey, data, timestamp}], count: number}. insert/update should return {success: boolean, id: string, timestamp: string}.
• Add constraint details to parameter descriptions: 'filter: Cosmos SQL WHERE clause (e.g., "c.status = 'active'")'; 'limit: max records to return (1-1000, default 20)'; 'data: object with string/number/boolean fields only'.
• Implement pagination: add offset/limit to query-records, return total_count, and cap default limit to 20. Document in description: 'Returns max 20 records per call; use offset for pagination.'
• Enhance error messages with recovery guidance: 'Partition key not found. Available keys: [list]. Try query-records with a valid key.' Categorize errors: retryable (timeout, rate limit) vs user-fixable (invalid partition key) vs fatal (auth failure).