aggregate_news

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

无任何注释，描述需承担行为披露责任。描述说明了去重合并行为、返回内容包含去重统计和平台覆盖统计，但未提及是否有副作用（如触发抓取）、是否需要提前抓取数据、是否有速率限制等。对于只读聚合工具，基本行为已透明，但缺少额外细节。

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?

描述以标题、Args、Returns、Examples分节，结构清晰，每个句子都有信息量，没有冗余。参数说明采用列表形式，并给出两个示例调用，简洁易读。

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?

所有参数均有解释，返回结构有概述，且有示例。存在输出schema，因此无需详述返回字段。唯一小缺失是date_range的具体格式（允许字符串或对象但未举例），但整体信息足够代理正确调用。

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的覆盖率为0%，但描述对所有5个参数都做了详细说明，包括类型、默认值、示例和含义（如similarity_threshold范围0.3-1.0，include_url控制是否包含链接）。描述完全补偿了schema的缺失，参数语义非常清晰。

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?

描述以明确的动词'聚合'和资源'新闻'开头，说明将相似新闻去重合并，并显示跨平台覆盖和综合热度。与兄弟工具如search_news、get_latest_news相比，功能边界清晰，可直接区分。

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?

描述通过功能说明隐含了使用场景（跨平台新闻去重聚合），但未明确说明何时应使用此工具而非其他工具（如search_news或find_related_news），也没有给出排除条件。缺乏显式的when/when-not指引。

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