Server has 19 tools with consistent naming (verb_noun pattern: page_read, page_create, grid_row_add) and complete input schemas with type constraints (gt, ge, le). Descriptions are present but brief (avg ~40 chars), lacking context on WHEN to use each tool or dependencies between them. Parameters are well-typed with constraints, but descriptions are minimal, e.g., 'Wiki page numeric ID' without explaining what distinguishes page_id from slug. Output schemas are not documented in the provided code. Error handling is present (errorReporting=true) but recovery guidance is not visible. Security is strong: no credentials in parameters, OAuth support, and read-only mode available. Composition is good, tools are single-responsibility and chainable (e.g., page_read returns page_id for use in page_update). Missing: output schema documentation, richer parameter descriptions, and error recovery examples.

• Document output schemas for all tools. Example: 'page_read returns {page_id: int, title: string, content: string, breadcrumbs: array}'. This enables LLMs to chain tools correctly.
• Expand parameter descriptions to 50-100 chars with dependency hints. Example: 'Wiki page numeric ID (required if slug not provided; mutually exclusive with slug).'
• Add WHEN-to-use context to tool descriptions. Example: 'Use page_read for a single page's full content; use page_traverse to list child pages; use page_resources_read to fetch only attachments.'
• Implement confirmation pattern for destructive operations. Add a dry_run parameter or require explicit confirmation via a separate confirm_delete tool.
• Enhance error responses with recovery guidance. Example: 'Permission denied: you lack write:wiki scope. Contact your admin or use read-only mode.'

Inferred effective spec: 2026-07-28+.

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)