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

Beyond the annotations (readOnly, idempotent, openWorld, non-destructive), the description discloses result ordering (time descending), the returned fields (note ID plus basic engagement metrics), and the billing model: ¥0.2 per successful call, with failures and empty results refunded. That pricing and refund policy is operationally important context an agent could not infer from structured fields.

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?

Four short sentences ordered from purpose to return shape to when-to-use to cost, with no filler. It is slightly dense with clauses, but every sentence carries distinct information.

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 no output schema, the description still communicates return ordering and returned fields, and it covers pagination and billing for a 3-parameter read tool. Only the exact shape of the engagement metrics is left unspecified.

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 coverage is 100%, with both userid and cursor documented in the schema itself. The description adds only that pagination is supported and that results are time-descending, which hints at cursor semantics but gives no format detail beyond the schema; baseline 3 is appropriate.

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 first sentence states a specific verb and resource (获取用户发布的笔记列表) plus the scope (a single account's published notes, time descending). This clearly separates it from xhs_note_search (keyword search) and xhs_note_detail (single note), although neither sibling is named explicitly.

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 names three concrete use cases: monitoring an account's posting frequency, observing content strategy, and bulk-collecting note IDs. It does not state when NOT to use it or point at a sibling tool for single-note or search needs, so it stops short of a 5.

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