minimax_delete_task

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. While 'Delete' implies mutation, the description does not specify whether deletion is permanent, whether it requires any confirmation or special permissions, or whether it can fail under certain conditions. It also doesn't mention what happens to the task data or resources.

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, compact sentence that conveys the essential purpose without any fluff or redundancy. It is appropriately front-loaded and efficient.

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 tool's relative simplicity (one parameter, no nested objects, clear action) and the presence of an output schema, the description is adequate but not rich. It does not fully compensate for the lack of annotations, particularly around behavioral risks like permanence. However, the output schema may provide some post-deletion context that is not visible here.

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 100% for the single parameter (task_id) with a clear description 'The task ID to delete.' The tool description adds no additional meaning beyond that, but the schema already sufficiently documents the parameter.

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 verb ('Delete') and resource ('a MiniMax video generation task'). It is specific and distinguishes from siblings (e.g., minimax_get_task for retrieval, minimax_list_tasks for listing). However, it doesn't elaborate on the scope or effect of deletion beyond the basic 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?

The description implies usage for deleting tasks, but does not provide explicit guidance on when to use it vs. alternatives. It doesn't mention context like how to obtain the task_id or whether deletion is permanent, nor does it exclude any scenarios. Sibling tools are not referenced.

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