get_zhihu_question

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

The description discloses the prerequisite of logging in and the need for a specific parameter (question_id from xsec_token). It implies read-only behavior ('获取' means fetch), but does not mention rate limits, error handling, or other constraints. Annotations are absent, so the description carries full burden, which it partially meets.

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 extremely concise, using two sentences: the first states the purpose, the second provides prerequisites. Each sentence adds value without 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?

While the description effectively conveys the main purpose and prerequisites, it omits explanations for the limit and max_content_length parameters. Given the tool has three parameters and no schema descriptions, the description is not fully complete. An output schema exists but doesn't alleviate the need for parameter clarification.

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?

The description adds meaning only for the question_id parameter, explaining it comes from search results. It does not explain the limit or max_content_length parameters. With 0% schema description coverage, the description should compensate but fails to cover two out of three parameters.

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 explicitly states the tool fetches details and top N answers of a Zhihu question, using clear verb and resource. It distinguishes from sibling tools like search_zhihu (searching) and login_zhihu (authentication) by implying this tool is used after searching and logging in.

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 provides clear context: login is required first, and the question_id comes from search results. This implicitly guides when to use the tool (after login and search) but does not explicitly mention alternatives or scenarios where it should not be used.

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