xhs_note_detail

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

No annotations are provided, so the description must disclose behavioral traits. It lists return content and ID source but does not mention whether the operation is read-only, requires authentication, has rate limits, or how errors are handled. This is a significant gap for a data-fetching tool.

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?

Two succinct sentences: the first defines the tool's purpose, the second provides a usage tip. No redundant wording or unnecessary detail; every sentence earns its place.

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?

Despite lacking annotations or an output schema, the description enumerates the return contents (content, images, engagement metrics, author info, tags) and specifies the input source. For a simple one-parameter tool, this provides sufficient operational context, though edge cases and error handling are not covered.

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 already describes note_id fully ('Xiaohongshu note ID (from search results or URL)') with 100% coverage. The description only repeats this, adding no new semantic meaning. Baseline of 3 is appropriate since the schema carries the burden.

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?

Description clearly states the action ('Get full detail') and resource ('specific Xiaohongshu note by ID'), distinguishing it from sibling tools like xhs_search or xhs_user_profile. The verb+resource combination is specific and unambiguous.

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 guidance on where to obtain the note_id ('Use note IDs from xhs_search results'), giving practical usage context. Does not formally enumerate alternatives or exclusions, but sibling tools have distinct purposes, making the intended use clear.

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