Get Xiaohongshu note detail

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds a critical behavioral detail: settlement of ~0.01 USDC per successful call via x402, which is not covered by the annotations and is essential for the agent to disclose to the user. No contradiction 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 efficient—two sentences that cover purpose, trigger, and cost. It is front-loaded with the primary action and resource, and every sentence adds necessary information without verbosity.

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 readOnlyHint, openWorldHint, and idempotentHint annotations, plus the explicit description and parameter schemas, the agent has enough context to invoke the tool correctly. The return fields are stated in the description, and sibling tools are clearly distinct by resource and purpose.

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?

Both parameters are well-described. 'note' includes an explicit example URL and notes the 24-character hex format. 'note_type' explains its purpose as an optional media hint. Schema coverage is 100%, so nothing is left undefined.

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 specific resource (Xiaohongshu note), the action (fetch by URL or note_id), and the return fields (title, description, author, engagement stats, images, video URL). It distinguishes the tool from siblings such as xhs_get_user_notes by naming the exact input types.

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?

Provides explicit trigger conditions: 'Call this when the user pastes an xiaohongshu.com/explore link or a note id.' This gives clear direct guidance for when to use the tool and implies when not to (e.g., when a user ID is provided, use xhs_get_user_notes).

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