xhs_note

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds 'one' to clarify the scope and mentions xsec access parameters, but provides no additional behavioral details about errors, rate limits, or response structure. This is consistent with annotations, so no contradiction.

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 a single, front-loaded sentence of 10 words. Every word contributes meaning; no fluff.

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?

With one parameter, a rich annotation set, and an output schema present, the description covers the core purpose and input requirements. The only minor gap is a lack of clarification about error behavior or what constitutes a valid xsec URL, but overall it's sufficient for a simple read tool.

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?

The schema has one parameter 'url' with zero description coverage. The description compensates by specifying 'explore-note URL with its xsec access parameters', giving key semantic guidance about the expected URL format. However, it doesn't fully define the exact structure or require xsec, so a 4 is warranted.

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 uses the specific verb 'Read' and names the resource 'Xiaohongshu explore-note URL with its xsec access parameters'. It clearly distinguishes from sibling tools like xhs_search (search) and xhs_user_notes (user note lists) by focusing on a single URL-based read.

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?

The description implies the use case: when you have a specific explore-note URL to read. It provides clear context but doesn't explicitly mention alternatives or exclusions. There is no statement like 'use xhs_search instead for queries', so it falls short of explicit when-not guidance.

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