xhs_search_feeds

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

With no annotations, the description carries the full burden. It discloses the output structure and downstream usability of the returned IDs, which is useful. However, it does not mention whether login is required, error behavior, sorting/pagination, or rate limits, leaving notable gaps in behavioral transparency.

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 two concise sentences, front-loaded with the primary action and followed by useful output details. Every sentence earns its place, with no redundancy or fluff.

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?

Given the tool has no output schema and no annotations, the description provides essential information about what is returned and how to use the results. However, it omits authentication requirements, pagination/ordering behavior, and potential error scenarios, so it is not fully complete for a robust agent interaction.

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 100%: both keyword and limit have descriptions. The description adds minimal parameter-level meaning beyond the schema (it restates keyword-based search), so a baseline of 3 is appropriate without additional enrichment.

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 '搜索小红书笔记' (search Xiaohongshu notes) with a specific verb and resource, and lists the exact returned fields (ID, xsecToken, title, author, interaction data). This clearly distinguishes it from sibling tools like xhs_get_recommend_feeds or xhs_get_feed_detail by emphasizing keyword-based search.

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 provides clear context for when to use this tool (keyword search) and even explains how the returned id+xsecToken can be used with related tools. However, it does not explicitly mention alternatives or exclusions (e.g., 'use xhs_get_recommend_feeds for browsing'), but the purpose is clear enough for an agent to choose appropriately.

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