search_xiaohongshu

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

With no annotations, the description carries full burden. It discloses the login requirement and login_required error, and mentions returned fields. However, it does not state whether the operation is read-only, any rate limits, pagination, or other side effects. Adequate but not comprehensive.

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?

Three sentences, front-loaded with purpose and return info, then usage guidance. No redundant words. Highly efficient.

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?

The description covers basic purpose, return fields, and login requirement, but misses explanations for all parameters and possible behaviors like pagination or sorting. Given an output schema exists (not shown), it's acceptable but could be more thorough.

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%, and the description only adds a limit suggestion. It does not explain the query or note_type parameters, nor their expected formats or values. The description fails to compensate for the lack of schema descriptions.

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 and lists returned fields (title, URL, author, likes). It distinguishes from sibling tools like get_note_detail (which gets a single note) and search_zhihu (different platform).

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 explicitly recommends limit 10-20 and states the login prerequisite (login_xiaohongshu) and error behavior when not logged in. It lacks explicit when-not-to-use or alternatives, but still provides clear context.

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