zhihu_question_answers

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

无annotations，但描述仅说明基本功能，未提及分页、需登录状态或返回值结构等行为细节。

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?

两句话简洁明了，无冗余信息，关键信息前置。

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?

参数简单且有输出schema，但缺少行为细节，对于简单工具基本足够。

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覆盖100%，描述额外解释了question_id的来源，增加了参数上下文价值。

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?

描述明确使用动词'获取'和资源'知乎问题下的回答列表'，与兄弟工具如zhihu_answer、zhihu_comments等清晰区分。

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?

提供了从zhihu_search获取question_id的指引，但未明确说明何时不使用或与zhihu_answer的替代关系。

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