dingtalk_calendar_event_list

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

With no annotations provided, the description must fully convey behavioral traits. While '查看' implies a read-only operation, the description does not disclose return format, pagination, timezone handling, or any side effects. It adds little beyond the tool name and 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?

The description is a single concise sentence with no redundant words. It directly states the tool's function in a compact form, earning high marks for efficiency.

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?

For a simple list tool with two parameters and no output schema, the description covers the main purpose but leaves gaps: it does not mention what the return list contains, whose calendar is accessed, or timezone handling. It is adequate but not fully complete for an agent to predict all behaviors.

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?

The input schema provides 100% coverage for both parameters, including ISO 8601 format and default value for start_time. The description only generically refers to a 'specified time period' without adding deeper meaning or clarifying the relationship between start_time and end_time.

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?

The description clearly states the action (查看/list) and the resource (日程列表/calendar event list) with a specific time-range scope (指定时间段). It distinguishes this tool from singular event retrieval (dingtalk_calendar_event_get) and other calendar operations by emphasizing the list aspect.

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?

The description implies usage when a list of events in a time period is needed, but it provides no explicit context for when to use this tool versus alternatives like calendar_busy_search or calendar_event_get. There is no mention of exclusions or preferred scenarios.

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