list_available_dates

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

无注解，描述承担完全责任。说明了返回结果为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?

结构清晰：摘要有中英文，然后是Args、Returns、Examples。虽然包含中英双语略长，但信息完整且前置了关键目的。

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?

工具简单（1参数），描述涵盖了参数选项和示例。存在输出模式（虽未提供），但描述提示了返回JSON日期列表及比较结果，足够用于调用。

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?

输入模式仅有source参数且无枚举值，描述补充了三个有效值及其含义，增加了模式之外的语义。模式描述覆盖率为0%，描述充分补偿。

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?

明确陈述了工具功能：列出本地和远程可用的日期范围。使用了具体动宾结构（列出+可用日期范围），并与兄弟工具（如resolve_date_range）自然区分。

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?

提供了使用示例和参数说明，但没有明确说明何时避免使用或与兄弟工具的替代关系。上下文信号中兄弟工具列表暗示了相关但有区别的工具。

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