The server provides 21 tools with consistent naming, basic descriptions, and visible schemas. Naming follows verb_noun convention (list_, get_, create_, update_, delete_, search_) which is good. Descriptions exist for all tools but are brief (avg ~40 chars, below the 194-char baseline for A+ tools). All tools have input schemas with parameter types, though parameter descriptions are minimal. Output schemas are not documented, the rubric baseline shows 100% of A+ tools document return types, and this server has no documented outputs. No tool annotations (readOnlyHint/destructiveHint) despite risk labels being assigned in metadata. Composition is reasonable, tools are single-responsibility and chainable (e.g., list_items → get_item → update_item). Error handling is not visible in tool definitions. Parameter validation hints (ranges, enums, format constraints) are absent from descriptions despite several tools accepting strings and integers without bounds.

• Add comprehensive output schema documentation to every tool. Include field names, types, and descriptions. Example: 'Returns: {workspace_id: string, name: string, description: string, created_at: ISO8601, owner_id: string, ...}'. This allows LLMs to chain tools (e.g., create_workspace → list_items in that workspace).
• Expand tool descriptions to 100-200 chars with WHAT, WHEN, and any prerequisites. Example: 'List all workspaces accessible to the authenticated user. Useful for discovering available projects before creating items. Returns results paginated by limit/offset.' Include pagination details in description.
• Add numeric constraints to all integer parameters. Example: 'limit (integer, 1-100, default 20): Maximum number of results to return per page. Values outside this range will be clamped.' for nuclino_list_workspaces.
• Implement tool annotations for all destructive operations. Update tool definitions to include destructiveHint=true for nuclino_delete_workspace, nuclino_delete_collection, and nuclino_delete_item. Add readOnlyHint=true for all list_/get_/search_ tools.
• Add error recovery guidance to tool descriptions. Example: 'If workspace not found, call nuclino_list_workspaces to discover valid workspace IDs.' for nuclino_get_workspace. Document common failure modes (permission denied, not found, invalid state).
• Clarify parameter dependencies and mutual exclusivity. For nuclino_create_item, explicitly state: 'Either collection_id or parent_id is required. If both provided, collection_id takes precedence. parent_id is for nesting within items.' Document this in the tool description.

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry