xhs_search

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 does not disclose whether the tool requires authentication, is read-only, has rate limits, or any side effects. The limit parameter's max is stated, but overall behavioral context is lacking.

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 concise (a single line plus Args list) and front-loaded with the main purpose. However, it mixes English and Chinese, and the Args section could be more structured (e.g., using bullet points). Overall, it is efficiently worded.

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 an output schema exists, return values need not be described, but the description omits important context like authentication requirements, pagination, sorting order, and error handling. For a search tool, such details are significant.

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%, so the description compensates by explaining 'keyword' as search term and 'limit' as result count with default and maximum. However, it adds no additional format or constraints beyond what the schema already specifies (type and default).

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, which is a specific verb and resource. It distinguishes from siblings like xhs_get_note (specific note retrieval) and xhs_comment (commenting). However, it could be more explicit about the scope (e.g., full-text search vs. title 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 only implies usage for keyword-based search but provides no explicit guidance on when to use this tool vs. alternatives like xhs_get_note or xhs_user_profile. No exclusions or prerequisites are mentioned.

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