delete_task

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

No annotations are provided, so the description carries the full behavioral burden. For a destructive operation it says nothing about irreversibility, whether confirmation is needed, what the deletion affects (subtasks, reminders), or what is returned. It is essentially a restatement of the name plus the parameter.

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?

Very short and front-loaded: purpose first, then the parameter. It is not bloated, though the parameter block merely echoes the schema and could be trimmed.

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?

A destructive single-parameter tool with no annotations and no output schema needs more than one sentence: irreversibility, error behavior for an unknown ID, and side effects are all absent, leaving the agent underinformed before invoking a delete.

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 is 0%, so the description must compensate; it does so minimally by glossing task_id as the unique ID of the task to delete. That adds a little meaning (uniqueness, target identity) but omits format, source of the ID, or how to obtain one.

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?

States a specific verb+resource ('删除任务' / delete task) with an unambiguous scope, so an agent knows exactly what it does. However, it does not distinguish itself from siblings like update_task or complete_task, which are also task-state mutations.

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 when-to-use guidance, no prerequisite conditions, and no mention of alternatives such as complete_task (which may be preferable if the intent is to finish rather than remove a task). Only implied usage from the name.

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