xiaohongshu_search_articles

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

No annotations are provided, so the description carries the full burden. It discloses that the result comes from a '优质库' (quality database) and mentions pagination via 'offset', which adds behavioral context. However, it does not state whether the operation is read-only, if authentication is needed, or how results are sorted (sort_type is mentioned in schema but not explained).

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 very brief (two short sentences), which is concise but leaves out critical information (e.g., what the output contains, sort_type semantics). It is front-loaded with the core purpose but sacrifices completeness.

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 an output schema (not shown in detail), the description does not need to explain return values. However, with 3 parameters (one undocumented) and no annotations, the description is incomplete for a search tool. It lacks guidance on sorting, result limits, and the nature of '优质库'.

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 0%, and the description only elaborates on 'keyword' (required) and 'offset' (pagination). It does not explain 'sort_type' (default null, types string or null) – what sorting options exist or how it affects results. With 3 parameters and no schema descriptions, the description should provide more detail.

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 searches Xiaohongshu notes ('搜索小红书笔记') and specifies it uses a '优质库' (quality database). The verb '搜索' and resource '笔记' are specific, and the description distinguishes this from sibling search tools like xiaohongshu_search_users or xiaohongshu_search_ai_articles by the scope.

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 indicates 'keyword' is required and 'offset' is for pagination, implying usage for iterative searching. However, it does not explain when to use this tool versus the sibling xiaohongshu_search_ai_articles or other search tools, nor does it mention any prerequisites or limitations (e.g., rate limits or account requirements).

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