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

Annotations only cover safety (readOnlyHint, openWorldHint). The description goes well beyond by disclosing that one note can yield multiple image results, that the next page is not guaranteed to contain results, that ordering is platform-relevance based, and that keyword containment and full recall are not guaranteed — unusually rich operational caveats.

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?

Front-loaded with the core purpose, and every clause (result shape, pagination caveat, ranking, recall caveats, two alternatives) earns its place. It is delivered as one long semicolon-chained sentence, which is dense to parse but contains no filler.

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?

An output schema exists, so return values need no explanation. The description covers the remaining agent-relevant unknowns: item granularity, pagination behavior, ranking/recall limits, and routing to the two sibling search tools. Nothing material 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%, and the parameter descriptions already explain keyword constraints and page_token reuse rules in detail. The description restates page_token's purpose and adds only the caveat that the next page may be empty, which is marginal over the schema.

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?

States a specific verb+resource+scope: search Xiaohongshu images by keyword, and clarifies each result item is an image plus its associated note. It also explicitly differentiates itself from xhs_search_notes and xhs_search_videos, so an agent can select it without opening sibling schemas.

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?

Gives explicit routing: use xhs_search_notes(note_type="image") when image-text notes are wanted rather than single images, and xhs_search_videos for video. It also frames page_token as an optional continuation attempt. When-to-use and when-to-use-something-else are both covered.

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