delete_task_definition

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, and it discloses nothing: not that the operation is destructive and irreversible, not whether the task must be stopped or idle first, and not what happens to schedules or reports that reference the definition. For a deletion tool this is a critical 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 text is short and front-loaded, but the bilingual duplication of the same four words is pure redundancy rather than concision, and nothing substantive was trimmed to make room for it. This is under-specification, not efficient writing.

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, two-parameter tool with no annotations, no output schema, no documented parameters, and no description of side effects is completely inadequate for correct invocation. None of the context an agent needs before deleting a task definition is present.

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?

Two required parameters (robot_sn, fusion_task_id) exist with 0% schema description coverage, and the description supplies no meaning for either. The agent cannot tell what identifier format fusion_task_id expects or whether robot_sn scopes the lookup or identifies the executor.

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 is essentially a restatement of the tool name: '删除任务定义 / Delete task definition' adds no scope, target, or effect beyond the verb+resource already encoded in the identifier. It does not distinguish this tool from siblings like delete_schedule, update_task_definition, or list_task_definitions.

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 prerequisites, and no pointer to the related get/list/create/update_task_definition siblings. An agent receives no signal about when deletion is appropriate versus updating or merely listing.

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