xhs_get_recommend_feeds

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not mention authentication requirements (despite sibling login tools), potential rate limits, or any side effects. The description only lists return data, leaving crucial operational context unstated.

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, compact sentence that front-loads the main action and resource, then lists the return fields. It is efficient, with no redundant text or unnecessary detail.

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 read-only tool with one optional parameter, the description adequately covers purpose and return fields. However, it omits prerequisites like login and potential error scenarios, which could leave an agent unprepared despite the overall clarity.

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?

The sole parameter 'limit' is fully described in the schema (max count, default 10), so the description adds no extra parameter-specific meaning. Schema coverage is 100%, meaning the description does not need to compensate for missing parameter documentation.

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 retrieves the list of recommended notes from the Xiaohongshu homepage and enumerates the returned fields (ID, xsecToken, title, author, interaction data). This is a specific verb+resource operation that distinguishes it from siblings like xhs_search_feeds and xhs_get_feed_detail.

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 implies the tool is for browsing homepage recommendations but does not explicitly say when to use it over alternatives or any exclusions. The sibling context suggests it is used when a user wants recommended feeds, but no concrete guidance is provided.

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