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

With no annotations provided, the description carries full behavioral burden but discloses nothing: no read-only indication, auth requirements (_token or header), rating limits, pagination behavior, or result format. It leaves the agent without essential behavioral context.

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 one-phrase description is front-loaded and waste-free, but for a six-parameter tool with no annotations or output schema it is under-specified rather than appropriately concise. It essentially restates the tool name without adding structure or useful detail.

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 six parameters, no annotations, and no output schema, the description is incomplete. It omits return structure, pagination behavior, sort/time/type semantics, and authentication method, leaving an agent without enough context for reliable invocation.

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 all six parameters are already documented in the schema. The description adds no extra semantic detail about keyword handling, page, sort_type, note_time, note_type, or _token, so baseline 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?

States a specific verb (搜索) and resource (小红书笔记) with the keyword qualifier, so an agent can identify it as a keyword-based note search on Xiaohongshu. It does not distinguish itself from siblings like xhs_note or xhs_user, so it falls short of a 5.

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?

No guidance on when to use this tool versus alternatives such as xhs_note, douyin_search, or xhs_user, and no prerequisites or exclusions are mentioned. Search intent is implied only by the phrase itself.

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