RedNote MCP has critical definition gaps. Tool descriptions are present but minimal (10-20 chars in Chinese, below the 50-200 char LLM-optimized baseline). Input schemas are visible but lack parameter descriptions, the 'keywords' and 'limit' params in search_notes have descriptions, but the 'url' params in get_note_content and get_note_comments lack any explanation. The login tool has an empty input schema with no parameters documented. No output schemas are documented anywhere. Error handling is absent, no guidance on what happens on auth failure, network timeout, or invalid URLs. Tool naming is acceptable (verb_noun pattern), but composition is weak: login is a prerequisite for all other tools but this dependency is undocumented. No pagination support visible despite search_notes returning potentially large result sets.

• Add 50-150 character descriptions to each tool explaining WHAT it does, WHEN to use it, and any prerequisites. E.g. 'Search RedNote notes by keyword. Returns up to N results with title, author, and engagement metrics. Requires login() first.'
• Document all parameter formats: 'url' should specify 'Must be a valid xiaohongshu.com or xhslink.com URL' and 'limit' should specify 'Integer 1-100, default 10'.
• Add output schema documentation for each tool. For search_notes, document that it returns an array of Note objects with fields: title (string), content (string), author (string), url (string), likes (number), collects (number), comments (number).
• Add error handling guidance: 'If login fails, check credentials and network. If URL is invalid, verify it matches xiaohongshu.com/explore/... format. If rate limited, wait 60 seconds before retrying.'
• Document the login prerequisite in every tool description: 'Note: Requires successful login() call first. If not authenticated, this tool will fail with 'Not logged in' error.'