zhihu_list_user_activity

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

Beyond the readOnlyHint annotation, the description discloses behavioral details: content is pulled in descending publish time and stops when items are earlier than the target day, and it explicitly excludes full content and comments. It also mentions the default timezone (Asia/Shanghai), adding valuable context beyond what annotations provide.

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 three sentences, each with a clear purpose: the first explains purpose and output, the second provides cross-tool usage guidance, and the third covers ordering/stop behavior and url_token. Every sentence earns its place with 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 there is no output schema and 5 parameters (all fully described in the schema), the description covers the essential workflow: what is listed, what is excluded, how to use related tools, and the pagination logic. It is self-sufficient for selecting and invoking the tool correctly.

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%, so the baseline is 3. The description adds minor clarity by restating the date default (Asia/Shanghai) and the url_token definition (after /people/), but these are already present in the schema, so no significant extra semantics are provided.

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 uses a specific verb '发现' (discover/list) with a clear resource: a user's answers/articles/pins on a specified natural day. It explicitly states what is returned and what is excluded, and distinguishes itself from sibling tools by directing to zhihu_get_content for full content and zhihu_list_comments for hot 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 instructs to use zhihu_get_content for reading the full content and zhihu_list_comments for hot comments after obtaining the list, clearly indicating when not to use this tool. It also clarifies that this tool only returns list metadata, not full text or comments.

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