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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description adds real value on top: page-wise return semantics, per-call pricing of ¥0.2 with charge-on-success only and automatic refund on failure or empty results, plus a platform-imposed pagination depth ceiling past which upstream returns nothing. Those cost and truncation behaviors are exactly the operational facts an agent cannot infer from 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?

Roughly four sentences ordered purpose → output fields → use cases → cost and limits, with no filler. Each sentence carries a distinct decision-relevant fact, and the resource scope 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?

Despite having no output schema, the definition enumerates the returned fields and explains pagination and cost behavior, which is the full burden here. Nothing an agent needs in order to call this correctly on a read-only, per-page billed endpoint 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 description coverage is 100%, so the parameters are already documented and the baseline is 3. The description adds only indirect context for the start cursor ('按页返回' and the pagination depth limit); it says nothing about sort_strategy or the fallback _token auth parameter beyond what the schema states.

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?

States a specific verb+resource: 获取小红书笔记的一级评论列表, with the qualifier 一级 (top-level) that separates it from the sibling xhs_sub_comments. It also enumerates what comes back (正文、点赞数、回复数、昵称与地区、时间戳), so an agent knows exactly what this returns without opening the schema.

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?

Gives three concrete scenarios (评论情感分析、竞品口碑对比、舆情监测) that tell the agent when this tool is the right pick. It does not explicitly say to use xhs_sub_comments for reply threads or name prerequisites, so routing to alternatives is only implied by the 一级评论 scoping.

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