search_zhihu

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

Discloses requirement for authentication and specific error response. No annotations provided, so description carries burden. Describes return fields (title, URL, type, likes, author). Could mention pagination or sorting, but adequate for basic transparency.

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?

Two sentences: first states purpose and scope, second covers prerequisite and return info. No filler, front-loaded.

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?

Describes return fields and prerequisite, but lacks details on pagination, sorting, complete error scenarios, and output schema (though output schema exists). Moderately complete for a search tool.

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 has 0% description coverage. The description does not explain the 'limit' parameter or its default value. Only 'query' is implied. Parameter semantics are insufficient.

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?

Clearly states the verb '搜索' (search), resource '知乎内容' (Zhihu content), and scope '问答、专栏、视频' (Q&A, columns, videos). This distinguishes it from sibling tools such as search_xiaohongshu.

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?

Explicitly mentions prerequisite of logging in via login_zhihu and error behavior if not logged in. Also states what information is returned. However, it does not compare to alternatives like get_note_detail or get_zhihu_question.

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