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

No annotations are provided, so the description carries the full behavioral burden. It discloses the output shape (heat-sorted Chinese digest) but omits key behaviors: the default mark_seen=true means it writes to a seen-library and alters future results, and that side effect is never surfaced in the description. No mention of rate limits, auth, or reversibility.

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 compact sentences with the core action and output front-loaded, then the accounts format detail. Every clause earns its place; no padding.

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?

There is no output schema, and the description compensates partially by naming the return (heat-sorted Chinese daily digest). But with no annotations and a state-mutating default (mark_seen), the description is only marginally sufficient for correct invocation.

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 and the schema already documents all five parameters. The description restates the accounts format (comma-separated or preset packages, mixable), adding a small amount of framing but nothing the schema does not already contain.

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+resource (扫描 X 账号帖子) and the produced artifact (按热度排序输出中文资讯日报), which is concrete and informative. It self-labels as 核心工具, helping the agent prioritize it. However it does not explicitly distinguish itself from the sibling search_x_news, so it stops short of a 5.

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 '（核心工具）' tag implies this is the primary/aggregate tool versus siblings like get_post and search_x_news, giving implied usage context. But there is no explicit when-to-use, when-not-to-use, or named alternative, so guidance remains inferential.

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