xiaohongshu_comments

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

No annotations are present, so the description carries the full burden. It discloses important behaviors: only returns first screen (~10-20 comments), requires local Chrome + login cookie, and dependencies on search tokens. This gives an agent a good sense of the tool's constraints, though it doesn't mention failure modes.

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 crisp sentences with no filler; the main action is front-loaded, followed by prerequisites and parameter provenance.

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 simple comments-fetching tool, the description covers the essential context: what it returns, prerequisites, and parameter source. An output schema exists, so return details are covered elsewhere.

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 both parameters with 100% coverage. The description adds value by stating they both come from the same search result, establishing their relationship and source, which aids correct invocation.

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 uses specific verb '获取' (get) with resource '小红书笔记的评论' (Xiaohongshu note comments), and adds scope '首屏，约 10-20 条' (first screen, ~10-20 items), clearly distinguishing it from note-level tools like xiaohongshu_note.

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?

States prerequisites: local Chrome and login cookie, and specifies that both parameters come from the same xiaohongshu_search result, providing clear context for when to use it. However, it doesn't explicitly contrast with sibling comment tools like zhihu_comments or provide when-not-to-use, so slightly below perfect.

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