dingtalk_todo_task_delete

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

Although the verb 'delete' implies destruction, the description provides no explicit details about irreversibility, permission requirements, or what happens to the task after deletion. With no annotations provided, the description carries the full burden but fails to disclose any behavioral traits beyond the base action.

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 phrase with no filler or redundant content. It is appropriately sized for a simple one-parameter delete operation and is front-loaded with the action and object.

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?

The tool is very simple, but without annotations or an output schema, the description should still mention context such as whether the task must exist, if the deletion is permanent, or any error conditions. The one-line description is insufficient to fully guide an agent in all situations.

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 schema covers the only parameter (task_id) with the description '任务 ID', providing full coverage. The tool description adds no additional meaning to the parameter, so the baseline score of 3 applies as schema already handles the semantics.

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 a specific verb (delete) and resource (todo task). It distinguishes from sibling operations like dingtalk_todo_task_done (mark done) and dingtalk_todo_task_update (update), leaving no ambiguity about the action.

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?

There is no guidance on when to use this tool versus alternatives such as dingtalk_todo_task_done or dingtalk_todo_task_update. The description does not state prerequisites, side effects, or indicate that it is for permanent removal rather than completion.

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