List Xiaohongshu user notes

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnly, openWorld, idempotent), the description discloses that each page settles ~0.01 USDC via x402, which is critical for agents to anticipate costs. It also states returns note summaries and next_cursor, making pagination behavior transparent. No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, covering purpose, output, usage, and cost in three sentences. No fluff or redundant wording; information is front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple two-parameter paginated list operation and presence of an output schema, the description provides all necessary guidance: what it does, when to use it, what it returns, and how pagination/costs work. No critical context is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with both user_id and cursor clearly described. The description reinforces pagination behavior but does not add significant new parameter meaning beyond the schema. Slightly above baseline because the description ties the cursor to the prior response's next_cursor.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool lists posted notes for a Xiaohongshu user_id and returns note summaries with pagination. It distinguishes itself from sibling xhs_get_note_detail by focusing on listing all notes for a user rather than retrieving a single note's detail.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use when the user asks for a creator's recent posts,' providing a clear trigger condition. It also mentions pagination via next_cursor and the cost per page, which helps agents decide whether to call this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.