xiaohongshu-ai-feed

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. It discloses the daily scanning cadence, engagement-based filtering, clustering, HTML output, cover images, metrics, and subscription support. It does not mention auth, rate limits, or exact delivery format, but the core behavior is clearly stated.

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 core behavior is front-loaded and useful, but the final trigger list repeats the same need multiple times: 'AI 小红书日报、小红书AI热点、AI小红书内容、小红书信息源、xhs ai feed'. This redundancy adds length without adding information.

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?

The tool has no output schema and no annotations, so the description must carry the load. It gives a good high-level picture and communicates the main deliverable (HTML report), but it leaves param effects and return structure unspecified. It is adequate for simple selection but not fully complete.

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 coverage is nominally 100%, but each parameter description is only the parameter name itself ('keyword', 'pageNum', 'pageSize'), so no real semantics are added. The description does not clarify how keyword is matched or what pagination defaults exist, so it earns the baseline 3 rather than higher.

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 states a specific function: it scans AI-related Xiaohongshu notes daily, ranks them by engagement, clusters them, and generates an HTML report. The 'AI' and '日报' framing clearly distinguishes it from sibling search, crawler, downloader, and analyzer tools.

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?

The description explicitly lists when to use it: when the user needs AI Xiaohongshu daily reports, AI hotspots, AI content, or an xhs AI feed. It does not explicitly mention alternatives or when-not-to-use conditions, so it stops short of a 5.

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