FRED Economic Data (Federal Reserve)

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

注解已声明只读、幂等特性，描述额外提供了API密钥配置要求，这是有用的行为信息。但未提及响应格式、速率限制或常见错误，附加值一般。

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?

描述结构清晰：先陈述目的，后给出API密钥警告，再列出参数及示例，最后补充常用系列列表。内容精炼，无冗余，每个部分都有价值。

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?

对于5个参数的工具，描述覆盖了参数细节和API密钥，但缺少输出片段的描述（无输出模式），也没有说明错误处理或限制。尽管注解补充了部分内容，但整体完整性仍有欠缺。

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?

模式描述覆盖率为100%，基线为3。描述在参数示例、常用系列列表和日期格式方面增加了超出模式的实用指导，尤其是series参数的说明和常见系列列举，提升了可用性。

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?

描述明确说明工具用于查询FRED经济数据库，涵盖800k+系列，并支持多系列查询。虽然很清晰，但未与同级工具ext_fred_series进行区分，因此减1分。

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?

描述未提供何时使用此工具而非其他数据源（如ext_imf、ext_oecd）的指导，也没有说明不适用的情况。缺乏使用上下文或替代方案比较。

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