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

Beyond annotations, the description discloses that derived topic words are not the official hot-search ranking, that output depends on session mode, and that the official list requires XHS_COOKIE. This adds meaningful behavioral context beyond the readOnlyHint/openWorldHint/destructiveHint 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 a single dense sentence that front-loads the tool's purpose and enumerates outputs and configuration behavior. Every clause carries useful information, though the structure could be improved with bullet points for readability.

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?

For a tool with no output schema and no required parameters, the description does a good job specifying what is returned, what is optional, and how authentication affects results. Minor gaps remain around behavior on invalid cookies or when with_hotlist is true without a cookie, but the overall context is sufficient for an agent to call it correctly.

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 description coverage is 100%, so the baseline is 3. The description adds the XHS_COOKIE context relevant to with_hotlist, but it does not explain the numeric parameters meaningfully beyond what the schema already documents.

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 aggregates Xiaohongshu hot topics and lists the exact output components: official homepage hot-recommend notes, derived topic words, session mode, and optionally the official hot-search list. It is specific and informative, though it does not explicitly differentiate itself from sibling trend tools like get_trending or discover_trending_topics.

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?

It provides useful condition-based guidance: guests can use it with zero configuration, and setting XHS_COOKIE adds the official hot-search list. However, it does not say when to choose this tool over the sibling trend-related tools or specify any exclusions, leaving selection largely to inference.

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