Scoring was not performed

• Document output schema for every tool. Use JSON Schema in a 'Returns' section of the description. Example: 'Returns: {note_id: string, title: string, content: string, created_at: ISO8601, tags: string[], parent_id?: string}'
• Expand parameter descriptions from 1-2 words to 1-2 sentences explaining purpose, valid values, and any constraints. Example: 'Note ID (string or number). For integer IDs, pass as number; for UUIDs, pass as string. Required.'
• Add constraints and examples to parameters lacking them. For since_id: 'Cursor for pagination. Pass the ID of the last note from the previous call, or omit for the first page.'
• Define default limits for list_ tools. Example: 'Returns up to 20 notes per page. Omit page param to get first page.'
• Add idempotency guidance to save_note: 'If id is provided and exists, updates the note (idempotent). If id is omitted or new, creates a new note.'
• Create an enum constraint for note_type param: enum=['plain_text', 'link', 'img_text']. Document when each is valid and what additional fields are required.
• Add error recovery hints to get_note, delete_note, and lookup tools: 'If note not found, try searching with list_notes or list_topics to find the correct note_id.'
• Document pagination response structure for list_ tools: 'Response includes total_count (total notes available) and has_more (boolean). Use returned note.id as next since_id to fetch the next page.'
• Clarify array parameter behavior. For batch_add_notes_to_topic and remove_note_from_topic: 'Accepts 1-100 note IDs per call. Returns per-item success/failure breakdown if some additions fail.'