查询中国新闻

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

注解已经声明 readOnlyHint=true 和 openWorldHint=true，描述额外补充了输出会被规范化、去重且可引用，这些是有价值的行为信息。未提及分页、速率限制或具体返回结构，但在已有注解覆盖下仍算充分。

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?

一句话概括了核心查询维度和输出特性，信息密度高且没有冗余。但所有内容挤在一个句子中，缺少分段或列举结构，可读性略受影响。

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?

工具包含 7 个参数且没有输出 schema 或参数描述，描述虽然点明了主要查询维度，但未说明返回结果的具体结构、排序含义、时间范围默认值、source_ids 用法或与其他聚合/搜索工具的选择关系。对于这样一个中等复杂度的搜索工具，信息不足以让智能体完全正确调用。

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%），描述通过“关键词、分类、来源和时间范围”间接映射了 query、category、source_ids、from/to，但对 sort、limit 的语义没有说明，也没有解释各枚举值的具体含义。描述部分补偿了 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_international_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?

描述隐含了按多种条件检索中国新闻的用途，但没有明确说明何时应使用本工具而不是 aggregate_china_news 或 search_international_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.