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

The readOnlyHint and openWorldHint annotations already establish that this is a safe, open-web read operation, so the description only needs to add context. It contributes the fact that pagination is supported, which is useful, but it says nothing about per-page result counts, rate limits, or result ordering. Solid but not rich beyond the annotations.

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?

One front-loaded sentence plus one short routing clause; the primary purpose comes first and the exclusion second. There is no redundant wording, and the pagination note is attached to the purpose rather than buried.

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?

With full schema descriptions, an output schema, and annotations already covering the safety and openness profile, the description covers everything needed to select and invoke the tool. The only minor gap is that it does not indicate result volume or ordering per page, which the agent may want when planning pagination.

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%, and the keyword and page_token properties are already documented in detail, including the instruction not to pass profile links, user_id, or page tokens as the keyword. The description adds no syntax or format detail beyond the schema, so the baseline of 3 applies.

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 gives a specific verb and resource combination ('按搜索词搜索小红书用户、账号或博主' — search Xiaohongshu users, accounts, or bloggers by keyword) and names the scope of what it returns. It also distinguishes itself from the sibling profile tools, so an agent can tell it apart from xhs_get_user_info_by_user_id or xhs_get_user_info_by_profile_url without opening either schema.

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?

It states both when to use it (keyword-based discovery) and when not to: '已有用户 ID 或主页链接时，使用用户资料工具' explicitly routes the agent to the user-profile tools when an identifier is already known. This is the exact routing information needed, though it names the alternative as a category rather than a specific tool name.

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