dingtalk_calendar_event_delete

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

No annotations are provided, and the description only states 'delete schedule' without disclosing side effects, permanence, permissions, or error behavior. For a destructive operation, this is a significant gap.

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 extremely concise, using a single verb-noun phrase with no redundant language. It is appropriately sized for a simple delete operation, though it could be slightly more informative without becoming verbose.

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?

Given the lack of annotations, output schema, and behavioral details, the description is incomplete for a delete operation. The agent has only the action and a parameter, with no information about return values, error handling, or side effects.

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 fully documents the single parameter event_id with description '日程 ID' (100% coverage). The tool description adds no additional semantic information about the parameter, such as how to obtain it or any constraints, so the baseline score of 3 applies.

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 specifies the action (delete) and the resource (calendar event). It is distinct from sibling tools like dingtalk_calendar_event_create/get/update/list, which have different verbs and resources.

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 provides no guidance on when to use this tool or alternatives. It does not mention prerequisites, such as whether the user must be the event owner, or when deleting is preferable to updating or canceling an event.

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