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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about pagination behavior (despite a cursor parameter), the auth requirement for the _token fallback, or rate limits. It only weakly implies a read operation by virtue of being a 'list'.

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?

It is a single short phrase with zero waste, but it is under-specified rather than concise—there is essentially no content to front-load. Size is appropriate only in the sense that nothing is padded.

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 4-parameter tool with no annotations and no output schema, a bare noun phrase is insufficient: nothing explains the cursor-based paging model, the auth path, or the sort strategies available. The structured fields cannot compensate because the description adds no coverage.

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% and all four parameters are documented in the schema, so the baseline of 3 applies. The description adds no syntax, format, or default details beyond what the schema already provides.

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 is a direct translation of the tool name (xhs_note_comments → 'Xiaohongshu note comments list'), restating the name rather than stating what the tool does. It conveys the resource (note comments) but no verb or scope, and offers no differentiation from siblings like weibo_comments or douyin_video_comments beyond the platform name already present in the tool name.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the alternative xhs_note tool for the note itself versus its comments. The agent must infer applicability entirely from the tool name.

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