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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the description need not re-explain read-only behavior. It does add useful traits beyond them: the result set is restricted to articles specifically (answers, thoughts, and videos are excluded), and multi-page reading is supported through page_token. It stops short of describing ordering, page size, or whether private or restricted articles appear.

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 with zero filler: the first establishes the resource and the page_token pagination, the second states the content-type exclusion. The core purpose is front-loaded and nothing is repeated or padded.

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?

With an output schema present and full schema coverage of both parameters, the description only needs to explain scope and continuation, which it does. What remains unstated — result ordering, page size, and behavior when a profile has no articles — is minor for a single-purpose read tool. The strict URL-format guidance lives in the schema, so the description does not need to repeat it.

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 description coverage is 100%, and the schema already gives exhaustive constraints on both profile_url (accepted link form, rejected identifier forms, reuse from search results) and page_token (opaque, must be passed back unmodified, reset on author change). The description only restates that page_token enables continued pagination, adding no meaning beyond the schema, so the baseline 3 applies.

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 a specific verb and resource — read the list of articles published by a Zhihu user, resolved from a profile URL. It then explicitly narrows scope (only articles, not answers, thoughts, or videos) and notes pagination via page_token. This clearly separates it from sibling tools such as zhihu_get_user_info_by_profile_url or zhihu_search_content.

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 line 'only returns articles, not answers/thoughts/videos' implies when the tool is the wrong choice, and the schema spells out that other result types route back to items[].profile_url / author.profile_url. However, the description itself names no alternative tool and gives no explicit 'use this when' rule for competing endpoints. Usage guidance is implied rather than stated.

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