History Today

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

描述提及数据来源（60s-api.viki.moe）且公开、零凭证，这增加了透明度；但未详细说明错误处理、速率限制或返回结构细节（有输出 schema）。未发现与注释矛盾（无注释）。

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?

schema 描述覆盖率为 0%，但描述完全补偿：清晰说明了 date 参数的格式（MM-DD 或 YYYY-MM-DD）和默认行为（省略则用今天）。远超 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?

描述清楚说明了资源（历史事件）、输出（标题、年份、简述）以及功能（列出某日的历史事件）。它明确区别于兄弟工具（random_poem、holiday_info、holiday_summary）。

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?

描述给出使用场景（历史问答、内容创作、文化类 AI 陪练），但未明确说明何时不使用或引用替代工具。提供了上下文，但没有排除规则。

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