Server has 7 tools with basic naming and descriptions, but significant gaps in schema completeness and parameter documentation. All tools have descriptions (10-200 chars range), but 5 of 7 tools lack complete input schemas in the visible code. The add_items tool has no documented input schema at all. Tool names follow verb_noun convention (list_, get_, search_, create_) which is good. However, parameter descriptions are sparse or missing, and output schemas are not documented. Error handling and recovery guidance are absent. The HTTP transport is current, but tool definitions appear inferred rather than explicitly registered with full schemas.

• Document the complete output schema for each tool. For list_boards, specify: [{id: string, slug: string, name: string, icon: string, visibility: enum, item_count: number}]. For search_items, include all fields returned so the LLM knows what to extract.
• Add full input schema to add_items. Define the items array structure: items: [{type: enum[text|link|checklist], content: string, title?: string}]. Specify constraints on array length, content length, and type-specific validation.
• Enhance parameter descriptions with format and validation rules. E.g., 'board_slug: 8-character alphanumeric identifier (e.g., a1b2c3d4). Use list_boards to discover valid slugs.' For content in create_note, specify: 'For type=checklist, provide JSON array: [{text: string, done: boolean}]'.
• Add error handling guidance to tool descriptions. E.g., 'If board not found, call search_boards(). If permission denied, verify you are a board member.' Include retryability hints for transient failures.
• Implement dry-run or confirmation for create_note and add_items. Add optional 'dry_run: boolean' parameter. When true, return a preview of what would be created without persisting. This prevents accidental data creation.

Inferred effective spec: <=2025-11-25.

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