zhihu_search

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

With no annotations provided, the description carries full burden. It reveals that the tool directly calls Zhihu's v4 search API without a browser, requires specific cookies, and is concurrency-safe. It does not cover error scenarios like cookie expiration or rate limits, but it transparently addresses the main behavioral aspects beyond the minimal.

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 multi-sentence but each sentence adds value: purpose, prerequisite, technical detail, and safety note. It is front-loaded with the core purpose. A more structured bullet-point format could improve readability, but it remains efficient and clear.

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 an output schema exists, return format is covered. The description addresses key aspects: purpose, required authentication, API method, and concurrency. It does not specify result type (e.g., that results include questions/articles as stated in purpose), but it is sufficiently complete for a search tool with two parameters.

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%, so baseline is 3. The description adds minimal extra meaning beyond the schema: keyword is '搜索关键词' and limit is '返回条数 (默认 10)'. This confirms the schema descriptions but does not enrich them further.

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 '搜索知乎内容（问题/文章）', which clearly identifies the verb (search) and resource (Zhihu content, specifically questions and articles). It distinguishes from sibling tools like zhihu_answer, zhihu_comments, and zhihu_question_answers by focusing on search rather than specific item retrieval.

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 explains prerequisites (valid login cookie, specific file path) and concurrency safety. It mentions that Zhihu has disabled guest search, so a cookie is required. However, it does not explicitly advise when to use this tool over other search tools or alternatives, though the platform context makes it clear.

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