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

Annotations already mark the operation read-only and open-world. The description adds useful behavior beyond annotations: pagination is supported, and continuing pages require keeping keyword unchanged and passing the previous next_page_token untouched. No contradiction with 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?

The description is two short clauses with no filler, opens with the core action, and front-loads the key routing guidance before pagination details.

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 search tool with a complete output schema, full parameter documentation, and sibling context, the description covers the use case, exclusions, and pagination behavior. Nothing essential for invoking it correctly is missing.

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 100%, so the baseline is 3; the schema already explains keyword and page_token semantics. The tool description mostly restates that keyword searches users, accounts, or bloggers and does not add new parameter-level meaning.

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 a specific action and resource: searching Xiaohongshu users, accounts, or bloggers by keyword, with pagination support. It also explicitly differentiates from user-profile tools when an ID or profile link is already available, helping an agent choose among siblings.

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 when to use the tool (keyword-based user search) and when not to (when a user_id or profile link is already known, use the user profile tool). The keyword parameter's 'do not pass profile link, user_id, or pagination token' further clarifies boundaries.

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