zhihu_get_content

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

Annotations already declare readOnlyHint=true. The description adds valuable context about supported URL formats and the specific metadata returned (author, publish time, likes, comment count), going beyond the annotation.

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 tightly written sentences: the first states the core function, the second details supported URL formats and redirects comment-related queries to another tool. No wasted words.

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 a single parameter, a read-only annotation, and support for multiple URL types, the description sufficiently covers the tool's scope and return expectations. Minor omissions like pagination or size limits are not critical for a simple retrieval 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?

The schema covering 100% of parameters already describes the 'url' parameter as a link. The tool description enriches this by listing the exact URL patterns accepted, providing meaning beyond the schema's minimal description.

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 reads content and metadata from Zhihu pins, column articles, and answers. It lists specific URL patterns, distinguishing it from sibling tools like zhihu_list_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?

The description explicitly directs users to use zhihu_list_comments for comments, providing a clear alternative. It defines the supported URL types, making it clear when to use this tool, though it doesn't discuss other potential alternatives or exclusions.

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