Compendium provides 15 tools with consistent naming (verb_noun pattern: documents.*, collections.*, records.*) and basic descriptions. All tools have input schemas with type definitions and parameter descriptions. However, descriptions are terse (avg ~40 chars, well below the 194-char baseline), lack context on WHEN to use each tool, and omit guidance on state-modifying consequences. Output schemas are not documented. Error handling is minimal, no recovery guidance or actionable error messages. The tool set is well-composed (single responsibility per tool, proper chaining via IDs), but lacks the depth expected for production use.

• Expand all tool descriptions to 100 - 200 characters. Include WHAT the tool does, WHEN to use it (vs. similar tools), and any prerequisites. Example: 'Delete a document and all its children. This is irreversible. Use moveDocument to reorganize without deletion. Requires write permission on the document.'
• Document output schemas for all list/query/get tools. Specify field names, types, and whether results are paginated. Example: 'Returns {documents: [{id, title, parentId, createdAt}], total: number}'.
• Add dry-run or confirmation parameters to deleteDocument, deleteCollection, and deleteRecord. Let agents preview what will be deleted before committing.
• Enhance queryCollection filter description with an example: 'Filters: [{propertyKey: "status", op: "is", value: "active"}]. Supported ops: is, is_not, is_empty, is_not_empty.'
• Add error handling guidance to tool descriptions. Example: 'Returns 404 if document not found (retryable with correct ID). Returns 403 if user lacks write permission (user-fixable: request access). Returns 500 on server error (retryable after delay).'