search_news

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

没有提供注解（如 readOnlyHint、destructiveHint），描述中没有明确说明授权需求/速率限制/副作用。描述补充了搜索结果内容（JSON结构），但安全与写操作等信息缺失。

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?

返回结果说明为JSON、包涵热榜和可选RSS feed；已提供输入schema、默认值和建议。存在相关兄弟工具和fetch场景，但未对返回结构做详细解释，且缺少annotation明文说明。

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字段本身序列覆盖率为0%，但文本描述对全部10个参数（query、search_mode、date_range、platformsaku、limit、sort_by、threshold、include_url、include_rss、rss_limit）都有解释，并附带默认值与示例，远优于贫乏的json 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?

描述以明确动词开头（'统一搜索接口'），说明统一搜索热榜和RSS，且参数覆盖多种搜索模式。虽然与同类工具相比有明显区分，但没有明确点名替代性工具。

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?

提供了使用建议：在自然语言日期前先用 resolve_date_range 获得精确范围，并在 include_rss 等参数上有默认行为。但未明确说明与同类工具的选用边界。

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