29 tools with explicit schemas and descriptions. Naming is verb-first and clear (get_, create_, update_, list_, move_, clone_). Descriptions are present but terse (avg ~30 chars, well below the 194-char baseline). Parameter descriptions exist but many are minimal ('Entry scope: dash | widget | dataset | connection | folder'). Schemas use proper JSON types (string, boolean, number, array, object, union). No enum constraints on scope/orderField/orderDirection despite fixed valid values. Output schemas are not documented. Error handling and recovery guidance absent. Security: no secrets in params (good), but no permission gates or audit trail declarations visible.

• Expand parameter descriptions to 50 - 150 chars. For 'scope', write: 'Entry type to list: dash (dashboard), widget (chart), dataset, connection, or folder. Omit to list all types.' For 'orderField', write: 'Sort by: title (alphabetical), createdAt (newest first), or updatedAt (most recently modified).'
• Document output schemas for all tools. E.g., 'Returns: {id: string, title: string, description: string, createdAt: ISO8601, createdBy: {id, name}, permissions: {canEdit, canDelete, canShare}}'. Include pagination fields (page, pageSize, total) for list tools.
• Convert scope, orderField, orderDirection, and mode parameters to JSON Schema enums. This enables schema validation and prevents hallucinated values.
• Add error handling guidance. E.g., 'If collection not found, returns 404 with message. Try list_collection_content() to discover available collections. If permission denied, returns 403, you lack write:collection scope.'
• Declare permission requirements and audit trail. Add to tool descriptions: 'Requires: write:collection. Logged: user_id, collection_id, old_title, new_title, timestamp.' This enables least-privilege agent configs and compliance audits.