calendar_get_events

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

无注释，但描述充分披露了行为：通过iCal订阅拉取解析、日期格式（YYYY-MM-DD北京时间）、默认范围、过滤逻辑、limit截断并标记truncated。无矛盾。

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?

无输出模式，但描述了返回截断标记。未说明返回字段，但考虑到是列表工具，基本够用。对iCal订阅来源的解释增加了上下文。

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_coverage为0%，但描述为所有5个参数提供了详细语义：start_date/end_date的默认值、organizer和keyword的匹配规则（子串、大小写不敏感）、limit的默认值和截断行为。完全补偿了结构描述不足。

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?

描述明确说明工具用于“获取日程列表”，动词+资源明确。虽然未明确与兄弟工具如calendar_search区分，但通过解释iCal订阅来源和参数过滤，用途清晰。

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?

描述详细说明了何时使用：按日期、组织者、关键词筛选日程。给出了默认行为（不传日期时的范围）和示例（organizer='phil.ren'），帮助选择是否使用此工具而非其他。还说明了limit默认值和截断行为，指导用户避免上下文溢出。

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