get_latest_rss

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

无注解，描述承担了行为披露责任。它说明了数据存储分离、多日查询、返回格式，以及include_summary参数带来的'节省token'行为。但未明确说明只读性质、权限要求或速率限制。对于get类工具，行为基本可预期，评分4。

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?

所有参数被解释，返回类型有说明，示例提供了用法。但缺少对输出格式的详细描述或异常情况。尽管没有输出schema，但提供了返回描述。整体完整。评分4。

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?

描述为每个参数提供了明确语义：feed列表、默认天数、返回条数限制、摘要选项。参数含义清晰，并有示例用法。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订阅数据”，并说明“与热榜分开存储”，足以与同类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?

描述说明RSS数据与热榜数据分开存储，按时间流展示，适合获取特定来源的最新内容，这提供了使用上下文。但未明确说明何时不应使用（例如何时选择get_latest_news），也未提及替代工具，因此建议性指导有限。

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